From spec-starter
Guides Claude to follow the spec-driven development pattern — reading from spec/, context/, and CLAUDE.md — when working inside a repository scaffolded with the spec-starter commands.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin spec-starterThis skill uses the workspace's default tool permissions.
When working inside a repository that uses the spec-starter layout, follow this pattern at the start of every session.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
When working inside a repository that uses the spec-starter layout, follow this pattern at the start of every session.
project-root/
├── spec/ # Development specifications
├── context/ # User preferences and domain context
├── decisions/ # Architectural decision records
├── iterations/ # Spec version snapshots
├── archive/ # Processed prompt files
└── CLAUDE.md # Project summary and instructions
spec/ for the latest specification:
spec/starter.md exists, use thatv2.md, v3.md, …), use the highest-numbered versionRead all files in context/:
context/index.md is the primary context filecontext/technology-stack.md) may be present — read them allContext informs your choices about tools, languages, style, and constraints. It is supplementary; do not surface it unless it is directly relevant to the current task.
The user's original prompt was likely captured via speech-to-text. When the user provides new input by voice, be alert for:
Infer the likely intended meaning when obvious; ask for clarification when ambiguous.
spec/v2.md, spec/v3.md, …)When a significant architectural or technical decision is made, create a record in decisions/ using a date-prefixed filename: YYYY-MM-DD-description.md.
Before large refactors, snapshot the current spec by copying it to iterations/ with a descriptive name and timestamp, so the project's evolution is traceable.