Loading...
Loading...
Found 51 Skills
Chinese functional specification creation tool used to convert natural language feature descriptions into structured functional specification documents. Supports automatic branch name generation, Git branch creation, specification file initialization, and quality verification. Trigger words include: "speckit specification", "functional specification", "create specification", "feature description conversion", "speckit-specify". Use this skill when users need to convert feature ideas into structured specifications.
Use when setting up speckit (Specification-Driven Development) in a repo — copies slash commands, templates, and optionally creates a project constitution.
Create or update project charters from interactive or provided principle inputs, ensuring all dependent templates remain synchronized. Applicable to project management, specification formulation, charter maintenance, and team collaboration scenarios. Trigger words include "speckit constitution", "create charter", "update charter", "project charter", "formulate specification", "team charter"
Define or update the project governing principles in .specify/memory/constitution.md
Windows 11 system management
Identify undefined areas in the current feature specification by asking up to 5 highly targeted clarification questions, and encode the answers back into the specification. Trigger words include: "speckit-clarify", "speckit clarification", "specification clarification", "feature clarification", "identify ambiguities", "clarify requirements".
Execute all tasks from the task breakdown to build the feature. Use after task generation to systematically implement the planned solution following TDD approach where applicable.
Convert tasks.md into GitHub issues in the current repository
Initialize the .specify/ directory structure for Spec-Driven Development in the current project
Validate cross-artifact consistency across spec.md, plan.md, and tasks.md (read-only)
Execute implementation phase-by-phase following tasks.md
Use when implementing a GitHub issue end-to-end — MANDATORY for all dev tasks; spawns a repo worker devbox through speckit phases.