[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78GXTFQVSCAAACYHDVAC6M7":3,"skill-same:01M78GXTFQVSCAAACYHDVAC6M7":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M78GXTFQVSCAAACYHDVAC6M7","feature-spec",null,"Scaffold and complete a Ganttee feature specification. Use when starting a new feature, writing a spec\u002Fepic\u002Fuser story, or defining acceptance criteria for the Gantt editor (tasks, groups, milestones, dependencies, resources). Bundles a spec template and the required section checklist.","sergehas\u002Fganttee","sergehas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55877559?v=4","01M78GWP103XC9MZP2826NNTF3","01M78GWP22QVFBQNG8FAPPHE7Z",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Ffeature-spec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: feature-spec\ndescription:\n  \"Scaffold and complete a Ganttee feature specification. Use when starting a new feature, writing a\n  spec\u002Fepic\u002Fuser story, or defining acceptance criteria for the Gantt editor (tasks, groups,\n  milestones, dependencies, resources). Bundles a spec template and the required section checklist.\"\nargument-hint: \"\u003Cfeature name or short description>\"\n---\n\n# Feature Spec\n\nProduce an implementation-ready specification for a Ganttee feature.\n\n## When to Use\n\n- Turning a feature idea into a written spec before coding.\n- Defining an epic, its user stories, and Given\u002FWhen\u002FThen acceptance criteria.\n- Capturing data-model (`.ganttee` schema) and host↔webview protocol impact.\n\n## Procedure\n\n1. Create `docs\u002Fspecs\u002F\u003Cfeature-slug>\u002FSPEC.md` from the\n   [spec template](.\u002Fassets\u002Ffeature-spec-template.md) (the folder holds `SPEC.md` and any\n   spec-specific companion docs).\n2. Fill every section. Follow\n   [feature-spec.instructions.md](..\u002F..\u002Finstructions\u002Ffeature-spec.instructions.md) for section rules\n   and the acceptance-criteria format.\n3. Ground the spec in the codebase: reference real types in `src\u002Fcommon\u002Fmodels\u002F`, messages in\n   `src\u002Fcommon\u002Fprotocol.ts`, and logic in `src\u002Fservices\u002F`.\n4. For any `.ganttee` shape change, bump `CURRENT_DOCUMENT_VERSION` in the spec and describe the\n   migration.\n5. Write acceptance criteria for happy paths **and** error paths (cycle rejection, dangling\n   dependencies, invalid dates). Ensure each is test-verifiable.\n6. Number every Risk and Open Question per the\n   [shared ID convention](.\u002Fassets\u002Fopen-question-ids.md), grouped by severity. Record every item as\n   Open, then resolve it inline or with an ADR reference when its decision is settled.\n7. Sync status badge with front matter `Status`: place the mapped badge directly under\n   `# Feature: \u003Cname>` and update it whenever `Status` changes.\n8. Hand the finished spec to the **Test Planner** agent for a coverage plan and to the\n   **Architecture Guard** agent for a boundary check.\n\n## ADRs\n\nADRs are not spec-scoped. Follow the [domain-modeling skill](..\u002Fdomain-modeling\u002FSKILL.md)'s\n[ADR-FORMAT.md](..\u002Fdomain-modeling\u002FADR-FORMAT.md) for when a decision warrants one (hard to reverse,\nsurprising without context, a real trade-off), its location (`docs\u002Fadr\u002F`), and its numbering. When a\nreview or implementation session writes one, list it under the spec's front matter `Related ADRs`\nand mark each risk or Open Question it resolves `**Resolved**` with a link to it. Most resolved\nitems won't meet the bar — resolve those inline instead (see\n[open-question-ids.md](.\u002Fassets\u002Fopen-question-ids.md)).\n\n## Reminders\n\n- User-facing strings are localized (`vscode.l10n.t()` \u002F `nls`).\n- Branch coverage must stay ≥ 90%.\n- Reason about UX in design terms (see the `design-philosophy` skill).\n- Use the shared ID convention for every _Risk_ and _Open Question_. Severity meanings and order are\n  defined by the [reporting standard](..\u002F..\u002Finstructions\u002Freporting-standard.instructions.md).\n","# Feature Spec\n\nProduce an implementation-ready specification for a Ganttee feature.\n\n## When to Use\n\n- Turning a feature idea into a written spec before coding.\n- Defining an epic, its user stories, and Given\u002FWhen\u002FThen acceptance criteria.\n- Capturing data-model (`.ganttee` schema) and host↔webview protocol impact.\n\n## Procedure\n\n1. Create `docs\u002Fspecs\u002F\u003Cfeature-slug>\u002FSPEC.md` from the\n   [spec template](.\u002Fassets\u002Ffeature-spec-template.md) (the folder holds `SPEC.md` and any\n   spec-specific companion docs).\n2. Fill every section. Follow\n   [feature-spec.instructions.md](..\u002F..\u002Finstructions\u002Ffeature-spec.instructions.md) for section rules\n   and the acceptance-criteria format.\n3. Ground the spec in the codebase: reference real types in `src\u002Fcommon\u002Fmodels\u002F`, messages in\n   `src\u002Fcommon\u002Fprotocol.ts`, and logic in `src\u002Fservices\u002F`.\n4. For any `.ganttee` shape change, bump `CURRENT_DOCUMENT_VERSION` in the spec and describe the\n   migration.\n5. Write acceptance criteria for happy paths **and** error paths (cycle rejection, dangling\n   dependencies, invalid dates). Ensure each is test-verifiable.\n6. Number every Risk and Open Question per the\n   [shared ID convention](.\u002Fassets\u002Fopen-question-ids.md), grouped by severity. Record every item as\n   Open, then resolve it inline or with an ADR reference when its decision is settled.\n7. Sync status badge with front matter `Status`: place the mapped badge directly under\n   `# Feature: \u003Cname>` and update it whenever `Status` changes.\n8. Hand the finished spec to the **Test Planner** agent for a coverage plan and to the\n   **Architecture Guard** agent for a boundary check.\n\n## ADRs\n\nADRs are not spec-scoped. Follow the [domain-modeling skill](..\u002Fdomain-modeling\u002FSKILL.md)'s\n[ADR-FORMAT.md](..\u002Fdomain-modeling\u002FADR-FORMAT.md) for when a decision warrants one (hard to reverse,\nsurprising without context, a real trade-off), its location (`docs\u002Fadr\u002F`), and its numbering. When a\nreview or implementation session writes one, list it under the spec's front matter `Related ADRs`\nand mark each risk or Open Question it resolves `**Resolved**` with a link to it. Most resolved\nitems won't meet the bar — resolve those inline instead (see\n[open-question-ids.md](.\u002Fassets\u002Fopen-question-ids.md)).\n\n## Reminders\n\n- User-facing strings are localized (`vscode.l10n.t()` \u002F `nls`).\n- Branch coverage must stay ≥ 90%.\n- Reason about UX in design terms (see the `design-philosophy` skill).\n- Use the shared ID convention for every _Risk_ and _Open Question_. Severity meanings and order are\n  defined by the [reporting standard](..\u002F..\u002Finstructions\u002Freporting-standard.instructions.md).\n",{"name":5,"description":7,"argument-hint":23},"\u003Cfeature name or short description>","develop","3656175f11e1e311838b52d29a39d3173c74e3d8",".github\u002Fskills\u002Ffeature-spec",0,"https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee","https:\u002F\u002Fgithub.com\u002Fsergehas","2026-11-08 07:43:24",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sergehas\u002Fganttee --skill feature-spec",{"tool":37,"command":38},"bunx","bunx skills add sergehas\u002Fganttee --skill feature-spec",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sergehas\u002Fganttee --skill feature-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Ffeature-spec\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"assets\u002Ffeature-spec-template.md","ASSET","资产文件",2102,"https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Ffeature-spec\u002Fassets\u002Ffeature-spec-template.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"assets\u002Fopen-question-ids.md",2122,"https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Ffeature-spec\u002Fassets\u002Fopen-question-ids.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M78GZ7BMMQP5DJ1AQ6355P0K","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M78GZ5SJJ8G7SB4VPERDM1B7","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M78GZ16YCV8G87V26BVTJZ2H","ux-css-layout","VS Code (and so Ganttee) CSS conventions, file organization, class naming, standard sizes, scrollable content, responsive layout, and text overflow\u002Fellipsis patterns. Use when writing CSS, building layouts, or fixing text truncation issues.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fux-css-layout\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M78GYYTPF0Z3SY412PCND261","to-questionnaire","Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fto-questionnaire\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M78GYVE71DN5EZ5ZFWTGFHZ2","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M78GYQFC5GFHC544FYDZBVYV","spec-router","Detect which spec-lifecycle agent a request needs (drafting, reviewing, implementing, or test planning a feature spec) and suggest the handoff — never acts without confirmation. Use whenever a message mentions a spec\u002Ffeature-spec file, a roadmap status, or spec review\u002Fimplementation\u002F draft\u002Ftest-plan intent, even without an explicit @agent mention.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fspec-router\u002FSKILL.md",[],[]]