feature-spec
Scaffold and complete a Ganttee feature specification. Use when starting a new feature, writing a spec/epic/user story, or defining acceptance criteria for the Gantt editor (tasks, groups, milestones, dependencies, resources). Bundles a spec template and the required section checklist.
- License 许可
- AGPL-3.0
- 所属仓库
- sergehas/ganttee
- 最近更新
- 2026-11-08
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- feature-spec
- description
- Scaffold and complete a Ganttee feature specification. Use when starting a new feature, writing a spec/epic/user story, or defining acceptance criteria for the Gantt editor (tasks, groups, milestones, dependencies, resources). Bundles a spec template and the required section checklist.
- argument-hint
- <feature name or short description>
02 资源文件 2
- 资产文件assets/feature-spec-template.md2.1 KB
- 资产文件assets/open-question-ids.md2.1 KB
03 SKILL.md 正文
Feature Spec
Produce an implementation-ready specification for a Ganttee feature.
When to Use
- Turning a feature idea into a written spec before coding.
- Defining an epic, its user stories, and Given/When/Then acceptance criteria.
- Capturing data-model (
.gantteeschema) and host↔webview protocol impact.
Procedure
- Create
docs/specs/<feature-slug>/SPEC.mdfrom the spec template (the folder holdsSPEC.mdand any spec-specific companion docs). - Fill every section. Follow feature-spec.instructions.md for section rules and the acceptance-criteria format.
- Ground the spec in the codebase: reference real types in
src/common/models/, messages insrc/common/protocol.ts, and logic insrc/services/. - For any
.gantteeshape change, bumpCURRENT_DOCUMENT_VERSIONin the spec and describe the migration. - Write acceptance criteria for happy paths and error paths (cycle rejection, dangling dependencies, invalid dates). Ensure each is test-verifiable.
- Number every Risk and Open Question per the shared ID convention, grouped by severity. Record every item as Open, then resolve it inline or with an ADR reference when its decision is settled.
- Sync status badge with front matter
Status: place the mapped badge directly under# Feature: <name>and update it wheneverStatuschanges. - Hand the finished spec to the Test Planner agent for a coverage plan and to the Architecture Guard agent for a boundary check.
ADRs
ADRs are not spec-scoped. Follow the domain-modeling skill's
ADR-FORMAT.md for when a decision warrants one (hard to reverse,
surprising without context, a real trade-off), its location (docs/adr/), and its numbering. When a
review or implementation session writes one, list it under the spec's front matter Related ADRs
and mark each risk or Open Question it resolves **Resolved** with a link to it. Most resolved
items won't meet the bar — resolve those inline instead (see
open-question-ids.md).
Reminders
- User-facing strings are localized (
vscode.l10n.t()/nls). - Branch coverage must stay ≥ 90%.
- Reason about UX in design terms (see the
design-philosophyskill). - Use the shared ID convention for every Risk and Open Question. Severity meanings and order are defined by the reporting standard.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wait-what
Stop. That last message did not land: re-pitch it.
ux-css-layout
VS Code (and so Ganttee) CSS conventions, file organization, class naming, standard sizes, scrollable content, responsive layout, and text overflow/ellipsis patterns. Use when writing CSS, building layouts, or fixing text truncation issues.
to-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
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.
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/feature-spec file, a roadmap status, or spec review/implementation/ draft/test-plan intent, even without an explicit @agent mention.