Expand description
GitHub Spec Kit, the reference format: .specify/ and specs/NNN-name/
with spec.md, plan.md and tasks.md. Parsing is the
speccoder-speckit crate’s; this adapter is the only runtime code that
knows Spec Kit’s paths and words.
Modules§
- bench
- The Spec Kit project
speccoder bench importwrites around an issue. - bug
- Bugs in Spec Kit’s layout. With the first-party
bugextension installed and enabled, a bug is the extension’s own.specify/bugs/<slug>/assessment.md, written by its assess skill — speccoder writes nothing there and only reads the person’s words back. Without it, the standing unitNNN-bugfixes: each bug a user story whose acceptance scenarios are the triad, an approved requirement in triad form and a task citing it, appended. - extensions
- Spec Kit’s installed extensions: the one reader of
.specify/extensions*.specify extension list --jsonwhen the CLI is installed (read-only), else the registry files it keeps. - hooks
- Spec Kit extension hooks around what speccoder runs.
- workflow
speccoder workflow install: speccoder as a Spec Kit workflow step type, and a workflow that uses it.
Structs§
Statics§
- MESSAGES
- What a person is told about a Spec Kit project.
- PLANNING
- Spec Kit’s planning skills.
- RULES
- Spec Kit’s intent and planning rules.
- SPECKIT
- The one instance.
- WORDING
- What the model is told about Spec Kit.
Functions§
- precondition
- What a Spec Kit worktree needs committed, given the repository-relative
.specifyand feature directories. - story_
section - The
### User Story Nsection for labelUSN, up to the next heading of the same or a higher level.