[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76VJSES17N06KR5PBXWCFCS":3,"skill-same:01M76VJSES17N06KR5PBXWCFCS":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M76VJSES17N06KR5PBXWCFCS","jira-epic",null,"Creates Jira epics for large features following Prowler's standard format. Trigger: When user asks to create an epic, large feature, or multi-task initiative.","davidcoachdev\u002Fdcfiles","davidcoachdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69812733?v=4","01M758C4BR16TAV1N47W319E9V","David H. Caycedo Blum.","01M758C4CCZA2ZYGA0BGMXCDRH",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fjira-epic\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: jira-epic\ndescription: >\n  Creates Jira epics for large features following Prowler's standard format.\n  Trigger: When user asks to create an epic, large feature, or multi-task initiative.\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.0\"\n---\n\n## When to Use\n\nUse this skill when creating Jira epics for:\n- Large features spanning multiple components\n- New views\u002Fpages in the application\n- Major refactoring initiatives\n- Features requiring API + UI + SDK work\n\n## Epic Template\n\n```markdown\n# {Epic Title}\n\n**Figma:** {figma link if available}\n\n## Feature Overview\n\n{2-3 paragraph description of what this feature does and why it's needed}\n\n## Requirements\n\n### {Section 1: Major Functionality Area}\n\n#### {Subsection}\n- Requirement 1\n- Requirement 2\n- Requirement 3\n\n#### {Another Subsection}\n- Requirement 1\n- Requirement 2\n\n### {Section 2: Another Major Area}\n\n#### {Subsection}\n- Requirement 1\n- Requirement 2\n\n## Technical Considerations\n\n### Performance\n- {Performance requirement 1}\n- {Performance requirement 2}\n\n### Data Integration\n- {Data source}\n- {Integration points}\n\n### UI Components\n- {Component 1}\n- {Component 2}\n\n## Implementation Checklist\n\n- [ ] {Major deliverable 1}\n- [ ] {Major deliverable 2}\n- [ ] {Major deliverable 3}\n\n## Diagrams\n\n{Mermaid diagrams for architecture, flow, data model, etc.}\n```\n\n## Epic Title Conventions\n\nFormat: `[EPIC] Feature Name`\n\n**Examples:**\n- `[EPIC] Findings View`\n- `[EPIC] Multi-tenant Support`\n- `[EPIC] Compliance Dashboard Redesign`\n- `[EPIC] GovCloud Support`\n\n## Required Sections\n\n### 1. Feature Overview\nBrief but complete description of:\n- What the feature does\n- Who uses it\n- Why it's needed\n\n### 2. Requirements\nOrganized by functional area:\n- Group related requirements together\n- Use clear headers and subheaders\n- Be specific and testable\n\n### 3. Technical Considerations\nAlways include:\n- **Performance**: Large dataset handling, pagination, caching\n- **Data Integration**: Data sources, APIs, relationships\n- **UI Components**: Reusable components, design system usage\n\n### 4. Implementation Checklist\nHigh-level deliverables that will become individual tasks:\n- Each checkbox = potential Jira task\n- Order by dependency (API before UI)\n- Include testing milestones\n\n## Diagrams\n\nUse Mermaid for:\n\n### Architecture Diagrams\n```mermaid\ngraph TB\n    UI[UI Components] --> API[API Endpoints]\n    API --> SDK[Prowler SDK]\n    SDK --> Cloud[Cloud Providers]\n```\n\n### Data Flow Diagrams\n```mermaid\nsequenceDiagram\n    User->>UI: Apply filters\n    UI->>API: GET \u002Ffindings?filters\n    API->>DB: Query findings\n    DB-->>API: Results\n    API-->>UI: JSON response\n    UI-->>User: Render table\n```\n\n### State Diagrams\n```mermaid\nstateDiagram-v2\n    [*] --> Pending\n    Pending --> InProgress: Start triage\n    InProgress --> Resolved: Mark resolved\n    InProgress --> Pending: Reset\n    Resolved --> [*]\n```\n\n### Entity Relationship Diagrams\n```mermaid\nerDiagram\n    FINDING ||--o{ RESOURCE : affects\n    FINDING }|--|| CHECK : \"belongs to\"\n    RESOURCE }|--|| ACCOUNT : \"belongs to\"\n    ACCOUNT }|--|| PROVIDER : \"belongs to\"\n```\n\n## Splitting Epic into Tasks\n\nAfter creating the epic, generate individual tasks using the `jira-task` skill:\n\n### Task Naming Pattern\nFrom epic `[EPIC] Findings View`, create:\n- `[FEATURE] Findings table with pagination (UI)`\n- `[FEATURE] Findings filters - provider and account (UI)`\n- `[FEATURE] Findings detail panel - Overview tab (UI)`\n- `[FEATURE] Findings detail panel - Resources tab (UI)`\n- `[FEATURE] Findings bulk actions - mute\u002Fsuppress (API + UI)`\n- `[FEATURE] Findings search functionality (API + UI)`\n\n### Task Dependencies\nAlways specify in each task:\n```markdown\n## Related Tasks\n- Epic: [EPIC] Findings View\n- Blocked by: [task if any]\n- Blocks: [task if any]\n```\n\n## Figma Integration\n\nWhen Figma links are provided:\n- Include main Figma link at top\n- Reference specific frames in relevant sections\n- Example: `https:\u002F\u002Fwww.figma.com\u002Fdesign\u002Fxxx?node-id=1830-44712&m=dev`\n\n## Output Format\n\n```markdown\n## Epic: [EPIC] {Title}\n\n{Full epic content following template}\n\n---\n\n## Suggested Tasks\n\nBased on this epic, create the following tasks:\n\n| # | Title | Component | Blocked By |\n|---|-------|-----------|------------|\n| 1 | [FEATURE] Task name | API | - |\n| 2 | [FEATURE] Task name | UI | Task 1 |\n| 3 | [FEATURE] Task name | UI | Task 2 |\n\nWould you like me to generate the full task descriptions?\n```\n\n## Checklist Before Submitting\n\n1. ✅ Title follows `[EPIC] Feature Name` format\n2. ✅ Feature Overview explains what\u002Fwho\u002Fwhy\n3. ✅ Requirements are organized by functional area\n4. ✅ Technical Considerations cover performance, data, UI\n5. ✅ Implementation Checklist has high-level deliverables\n6. ✅ Diagrams included where helpful (Mermaid format)\n7. ✅ Figma links included if available\n8. ✅ Suggested tasks table provided at the end\n\n## Formatting Rules\n\n**CRITICAL:** All output MUST be in Markdown format, ready to paste into Jira.\n\n- Use `#` for epic title, `##` for main sections, `###` for subsections\n- Use `**bold**` for emphasis\n- Use `- [ ]` for checkboxes in Implementation Checklist\n- Use ``` for code blocks and Mermaid diagrams\n- Use `backticks` for file paths, commands, and code references\n- Use tables for Suggested Tasks section\n- Use `---` to separate epic from suggested tasks\n\n## Jira MCP Integration\n\n**CRITICAL:** When creating epics via MCP, use these exact parameters:\n\n### Required Fields\n\n```json\n{\n  \"project_key\": \"PROWLER\",\n  \"summary\": \"[EPIC] Feature name\",\n  \"issue_type\": \"Epic\",\n  \"additional_fields\": {\n    \"customfield_10359\": {\"value\": \"UI\"}\n  }\n}\n```\n\n### Team Field (REQUIRED)\n\nThe `customfield_10359` (Team) field is **REQUIRED**. Options:\n- `\"UI\"` - Frontend epics\n- `\"API\"` - Backend epics\n- `\"SDK\"` - Prowler SDK epics\n\n### Work Item Description Field\n\n**IMPORTANT:** The project uses `customfield_10363` (Work Item Description) instead of the standard `description` field for display in the UI.\n\n**CRITICAL:** Use **Jira Wiki markup**, NOT Markdown:\n- `h2.` instead of `##`\n- `*text*` for bold instead of `**text**`\n- `* item` for bullets (same)\n- `** subitem` for nested bullets\n\nAfter creating the epic, update the description with:\n\n```json\n{\n  \"customfield_10363\": \"h2. Feature Overview\\n\\n{overview}\\n\\nh2. Requirements\\n\\n*{Section 1}*\\n* {requirement 1}\\n* {requirement 2}\\n\\n*{Section 2}*\\n* {requirement 1}\\n* {requirement 2}\\n\\nh2. Technical Considerations\\n\\n*Performance:*\\n* {consideration 1}\\n\\n*Data Integration:*\\n* {consideration 2}\\n\\nh2. Implementation Checklist\\n\\n* [ ] {deliverable 1}\\n* [ ] {deliverable 2}\\n* [ ] {deliverable 3}\"\n}\n```\n\n### Linking Tasks to Epic\n\nWhen creating child tasks, use the epic key as parent:\n\n```json\n{\n  \"additional_fields\": {\n    \"parent\": \"PROWLER-XXX\"\n  }\n}\n```\n\n### Workflow Transitions\n\n```\nBacklog (10037) → To Do (14) → In Progress (11) → Done (21)\n                → Blocked (10)\n```\n\n### MCP Commands Sequence\n\n1. **Create epic:**\n```\nmcp__mcp-atlassian__jira_create_issue (issue_type: \"Epic\")\n```\n\n2. **Update Work Item Description:**\n```\nmcp__mcp-atlassian__jira_update_issue with customfield_10363\n```\n\n3. **Create child tasks:**\n```\nmcp__mcp-atlassian__jira_create_issue with parent: EPIC-KEY\n```\n\n4. **Assign and transition:**\n```\nmcp__mcp-atlassian__jira_update_issue (assignee)\nmcp__mcp-atlassian__jira_transition_issue (status)\n```\n\n","## When to Use\n\nUse this skill when creating Jira epics for:\n- Large features spanning multiple components\n- New views\u002Fpages in the application\n- Major refactoring initiatives\n- Features requiring API + UI + SDK work\n\n## Epic Template\n\n```markdown\n# {Epic Title}\n\n**Figma:** {figma link if available}\n\n## Feature Overview\n\n{2-3 paragraph description of what this feature does and why it's needed}\n\n## Requirements\n\n### {Section 1: Major Functionality Area}\n\n#### {Subsection}\n- Requirement 1\n- Requirement 2\n- Requirement 3\n\n#### {Another Subsection}\n- Requirement 1\n- Requirement 2\n\n### {Section 2: Another Major Area}\n\n#### {Subsection}\n- Requirement 1\n- Requirement 2\n\n## Technical Considerations\n\n### Performance\n- {Performance requirement 1}\n- {Performance requirement 2}\n\n### Data Integration\n- {Data source}\n- {Integration points}\n\n### UI Components\n- {Component 1}\n- {Component 2}\n\n## Implementation Checklist\n\n- [ ] {Major deliverable 1}\n- [ ] {Major deliverable 2}\n- [ ] {Major deliverable 3}\n\n## Diagrams\n\n{Mermaid diagrams for architecture, flow, data model, etc.}\n```\n\n## Epic Title Conventions\n\nFormat: `[EPIC] Feature Name`\n\n**Examples:**\n- `[EPIC] Findings View`\n- `[EPIC] Multi-tenant Support`\n- `[EPIC] Compliance Dashboard Redesign`\n- `[EPIC] GovCloud Support`\n\n## Required Sections\n\n### 1. Feature Overview\nBrief but complete description of:\n- What the feature does\n- Who uses it\n- Why it's needed\n\n### 2. Requirements\nOrganized by functional area:\n- Group related requirements together\n- Use clear headers and subheaders\n- Be specific and testable\n\n### 3. Technical Considerations\nAlways include:\n- **Performance**: Large dataset handling, pagination, caching\n- **Data Integration**: Data sources, APIs, relationships\n- **UI Components**: Reusable components, design system usage\n\n### 4. Implementation Checklist\nHigh-level deliverables that will become individual tasks:\n- Each checkbox = potential Jira task\n- Order by dependency (API before UI)\n- Include testing milestones\n\n## Diagrams\n\nUse Mermaid for:\n\n### Architecture Diagrams\n```mermaid\ngraph TB\n    UI[UI Components] --> API[API Endpoints]\n    API --> SDK[Prowler SDK]\n    SDK --> Cloud[Cloud Providers]\n```\n\n### Data Flow Diagrams\n```mermaid\nsequenceDiagram\n    User->>UI: Apply filters\n    UI->>API: GET \u002Ffindings?filters\n    API->>DB: Query findings\n    DB-->>API: Results\n    API-->>UI: JSON response\n    UI-->>User: Render table\n```\n\n### State Diagrams\n```mermaid\nstateDiagram-v2\n    [*] --> Pending\n    Pending --> InProgress: Start triage\n    InProgress --> Resolved: Mark resolved\n    InProgress --> Pending: Reset\n    Resolved --> [*]\n```\n\n### Entity Relationship Diagrams\n```mermaid\nerDiagram\n    FINDING ||--o{ RESOURCE : affects\n    FINDING }|--|| CHECK : \"belongs to\"\n    RESOURCE }|--|| ACCOUNT : \"belongs to\"\n    ACCOUNT }|--|| PROVIDER : \"belongs to\"\n```\n\n## Splitting Epic into Tasks\n\nAfter creating the epic, generate individual tasks using the `jira-task` skill:\n\n### Task Naming Pattern\nFrom epic `[EPIC] Findings View`, create:\n- `[FEATURE] Findings table with pagination (UI)`\n- `[FEATURE] Findings filters - provider and account (UI)`\n- `[FEATURE] Findings detail panel - Overview tab (UI)`\n- `[FEATURE] Findings detail panel - Resources tab (UI)`\n- `[FEATURE] Findings bulk actions - mute\u002Fsuppress (API + UI)`\n- `[FEATURE] Findings search functionality (API + UI)`\n\n### Task Dependencies\nAlways specify in each task:\n```markdown\n## Related Tasks\n- Epic: [EPIC] Findings View\n- Blocked by: [task if any]\n- Blocks: [task if any]\n```\n\n## Figma Integration\n\nWhen Figma links are provided:\n- Include main Figma link at top\n- Reference specific frames in relevant sections\n- Example: `https:\u002F\u002Fwww.figma.com\u002Fdesign\u002Fxxx?node-id=1830-44712&m=dev`\n\n## Output Format\n\n```markdown\n## Epic: [EPIC] {Title}\n\n{Full epic content following template}\n\n---\n\n## Suggested Tasks\n\nBased on this epic, create the following tasks:\n\n| # | Title | Component | Blocked By |\n|---|-------|-----------|------------|\n| 1 | [FEATURE] Task name | API | - |\n| 2 | [FEATURE] Task name | UI | Task 1 |\n| 3 | [FEATURE] Task name | UI | Task 2 |\n\nWould you like me to generate the full task descriptions?\n```\n\n## Checklist Before Submitting\n\n1. ✅ Title follows `[EPIC] Feature Name` format\n2. ✅ Feature Overview explains what\u002Fwho\u002Fwhy\n3. ✅ Requirements are organized by functional area\n4. ✅ Technical Considerations cover performance, data, UI\n5. ✅ Implementation Checklist has high-level deliverables\n6. ✅ Diagrams included where helpful (Mermaid format)\n7. ✅ Figma links included if available\n8. ✅ Suggested tasks table provided at the end\n\n## Formatting Rules\n\n**CRITICAL:** All output MUST be in Markdown format, ready to paste into Jira.\n\n- Use `#` for epic title, `##` for main sections, `###` for subsections\n- Use `**bold**` for emphasis\n- Use `- [ ]` for checkboxes in Implementation Checklist\n- Use ``` for code blocks and Mermaid diagrams\n- Use `backticks` for file paths, commands, and code references\n- Use tables for Suggested Tasks section\n- Use `---` to separate epic from suggested tasks\n\n## Jira MCP Integration\n\n**CRITICAL:** When creating epics via MCP, use these exact parameters:\n\n### Required Fields\n\n```json\n{\n  \"project_key\": \"PROWLER\",\n  \"summary\": \"[EPIC] Feature name\",\n  \"issue_type\": \"Epic\",\n  \"additional_fields\": {\n    \"customfield_10359\": {\"value\": \"UI\"}\n  }\n}\n```\n\n### Team Field (REQUIRED)\n\nThe `customfield_10359` (Team) field is **REQUIRED**. Options:\n- `\"UI\"` - Frontend epics\n- `\"API\"` - Backend epics\n- `\"SDK\"` - Prowler SDK epics\n\n### Work Item Description Field\n\n**IMPORTANT:** The project uses `customfield_10363` (Work Item Description) instead of the standard `description` field for display in the UI.\n\n**CRITICAL:** Use **Jira Wiki markup**, NOT Markdown:\n- `h2.` instead of `##`\n- `*text*` for bold instead of `**text**`\n- `* item` for bullets (same)\n- `** subitem` for nested bullets\n\nAfter creating the epic, update the description with:\n\n```json\n{\n  \"customfield_10363\": \"h2. Feature Overview\\n\\n{overview}\\n\\nh2. Requirements\\n\\n*{Section 1}*\\n* {requirement 1}\\n* {requirement 2}\\n\\n*{Section 2}*\\n* {requirement 1}\\n* {requirement 2}\\n\\nh2. Technical Considerations\\n\\n*Performance:*\\n* {consideration 1}\\n\\n*Data Integration:*\\n* {consideration 2}\\n\\nh2. Implementation Checklist\\n\\n* [ ] {deliverable 1}\\n* [ ] {deliverable 2}\\n* [ ] {deliverable 3}\"\n}\n```\n\n### Linking Tasks to Epic\n\nWhen creating child tasks, use the epic key as parent:\n\n```json\n{\n  \"additional_fields\": {\n    \"parent\": \"PROWLER-XXX\"\n  }\n}\n```\n\n### Workflow Transitions\n\n```\nBacklog (10037) → To Do (14) → In Progress (11) → Done (21)\n                → Blocked (10)\n```\n\n### MCP Commands Sequence\n\n1. **Create epic:**\n```\nmcp__mcp-atlassian__jira_create_issue (issue_type: \"Epic\")\n```\n\n2. **Update Work Item Description:**\n```\nmcp__mcp-atlassian__jira_update_issue with customfield_10363\n```\n\n3. **Create child tasks:**\n```\nmcp__mcp-atlassian__jira_create_issue with parent: EPIC-KEY\n```\n\n4. **Assign and transition:**\n```\nmcp__mcp-atlassian__jira_update_issue (assignee)\nmcp__mcp-atlassian__jira_transition_issue (status)\n```\n\n",{"name":5,"license":15,"metadata":24,"description":27},{"author":25,"version":26},"gentleman-programming","1.0","Creates Jira epics for large features following Prowler's standard format. Trigger: When user asks to create an epic, large feature, or multi-task initiative.\n","main","5dc86f90a5cbe45db3acd917825461b3ed6937fb","config\u002F.config\u002Fopencode\u002Fskills\u002Fjira-epic",0,"https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev","🌐 Apasionado por crear soluciones web escalables y eficientes. \r\n🧑‍🏫 Coach Dev.\r\n💻 Frontend Dev. \r\n🎚️Backend Dev.\r\n📊 Agile\u002FScrum.\r\n🚀100% remoto.","2026-08-26 07:28:05",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add davidcoachdev\u002Fdcfiles --skill jira-epic",{"tool":42,"command":43},"bunx","bunx skills add davidcoachdev\u002Fdcfiles --skill jira-epic",{"tool":45,"command":46},"pnpm","pnpm dlx skills add davidcoachdev\u002Fdcfiles --skill jira-epic","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fjira-epic\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},".skill-meta.json","REFERENCE","参考文档",391,"https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fjira-epic\u002F.skill-meta.json",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"README.md",431,"https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fjira-epic\u002FREADME.md",[61,68,75,82,90,97],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7740FETMZY1VTYAEFY1TWY7","zustand-5","Zustand 5 state management patterns. Trigger: When managing React state with Zustand.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzustand-5\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M773ZZM9V68SA1AKP4WF4J29","zod-4","Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzod-4\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M773ZJFR90CQAY0N9QR40QVP","x-bookmark-quote-posts","Workflow para revisar bookmarks de X\u002FTwitter y convertirlos en drafts de quote posts. Accede a la sección de bookmarks vía browser headless, extrae posts recientes, y genera drafts con voz personal del usuario. No publica ni muta X — solo genera contenido para revisión. Trigger: X bookmarks, Twitter bookmarks, quote posts, bookmark automation, crear quote posts, revisar bookmarks, growth content X.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fx-bookmark-quote-posts\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M773Z2RGV3786FV310SDB0YD","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","MIT","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M773YJH3KDSW467CSS63CSRJ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M773Y3S3H2CPRK5S8YFHWB5C","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[]]