spec-kit-skill
SolidGitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow. Triggers: "spec-kit", "speckit", "constitution", "specify", ".specify/", "规格驱动开发", "需求规格".
Install
Quality Score: 90/100
Skill Content
Details
- Author
- feiskyer
- Repository
- feiskyer/claude-code-settings
- Created
- 10 months ago
- Last Updated
- 1 months ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
speckit-workflow
Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.
spec-driven-development
Spec-Driven Development (SDD) methodology based on GitHub's SpecKit. Use for structured AI-assisted development with constitutional governance, phased workflows, and multi-agent coordination. Implements 7-phase process from constitution to implementation.
spec-kit-claude-code-workflow
A conceptual skill for guiding the Spec-Kit + Claude Code development workflow
speckit-install
Install the SpecKit CLI and initialize the current repository for one or both coding-agent integrations (Claude Code, Codex CLI). Use when the operator says: 'install speckit', 'set up speckit', 'initialize speckit in this repo', 'add speckit to this project', 'specify init for me', 'install spec-kit', '$speckit-install', or has a repo with no .specify/ directory and wants to start using Spec-Driven Development. Detects existing installs and hands off to $speckit-upgrade rather than overwriting. Safe to run on any repo. Not for upgrading an existing speckit install ($speckit-upgrade), not for scaffolding a new spec on an already-installed repo ($speckit-scaffold-spec), and not for installing this plugin's own bundled Codex subagents (use $install for that).
speckit-coach
Helps with SpecKit / Spec-Driven Development problems. Use when the user is stuck on: a failing simplicity gate or gate-validator rejecting acceptance criteria, deciding which checklist domains apply (api, security, observability, data-integrity, resilience), writing testable acceptance criteria the gate accepts, decomposing a large feature into multiple specs, creating a multi-spec technical roadmap, understanding the consensus protocol or how phase gates work, the difference between specify plan and specify tasks, what each /speckit-<command> does, how the tdd-mandate preset changes the workflow, where grill-me or clarify fit in the SDD process, repairing an existing speckit-pro project, making template customizations upgrade-safe, or browsing, installing, configuring, or removing SpecKit community extensions, presets, hooks, or catalog entries (verify, doctor, review, archive, retrospective, jira, azure-devops, and the rest of the upstream catalog). Not for actually running autopilot ($speckit-autopilot),