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.
- License 许可
- AGPL-3.0
- 所属仓库
- sergehas/ganttee
- 最近更新
- 2026-11-08
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- spec-router
- description
- 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.
03 SKILL.md 正文
Spec Router
Point a spec-related request at the right agent, without ever moving it there yourself.
When to Use
- The user's request is about a feature spec (draft, review, implement, test-plan, status, roadmap)
but does not explicitly
@mentionone of the spec agents. - Ambiguous phrasing like "let's start on this spec" or "is this ready to build".
Procedure
- Identify the target spec. If a file/slug is named, use it; otherwise ask which spec (or read
docs/specs/ROADMAP.mdfor candidates if the request implies "the current one"). - Read the spec's front matter
Status(or the ROADMAP row if there is no spec file yet — anIntententry). - Map
Statusto the next step using the lifecycle in docs/specs/README.md:Intent→ drafting is done in general chat first; Spec Writer once there is enough to write down.Draft→ Spec Reviewer (or Spec Implementer directly, if the user wants to skip review).Reviewed→ Spec Implementer.Implementing/Implemented→ Spec Implementer (continuing work) or Test Planner (coverage check).Blocked/On Hold→ surface the paused state; ask whether to resume first.
- State the recommended agent and the transition it would perform, then ask for confirmation through the ask-questions tool — always include an option to not hand off (e.g. "just answer in chat instead").
- On confirmation, invoke the named agent as a subagent with the spec path/slug and the user's original request as context.
Constraints
- DO NOT edit any file — routing only.
- DO NOT change a spec's status or ROADMAP row.
- DO NOT skip the confirmation step, even when the mapping in step 3 is unambiguous.
- If subagent invocation is unavailable in the current surface, state the recommended agent name and let the user invoke it directly instead.
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.
setup-skills
Configure this repo for the engineering skills: set up its issue tracker and domain doc layout. Run once before first use of the other engineering skills.