Gaku Yasui
Community@gkuga
Gaku Yasui maintains GitHub spec-kit command skills enabling specification-driven feature development, from natural-language specs through planning, task generation, and GitHub issue conversion.
Agent Skills by Gaku Yasui
Showing 9 vetted skills indexed across 1 GitHub repositories.
gkugaspeckit-checklist
Generate requirements-quality checklists for spec-kit feature specifications.
gkugaspeckit-constitution
Create or update the project constitution and sync dependent spec-kit templates.
gkugaspeckit-implement
Executes implementation tasks defined in tasks.md following the spec-kit project plan.
gkugaspeckit-taskstoissues
Convert spec-kit tasks into dependency-ordered GitHub issues via the GitHub MCP server.
gkugaspeckit-clarify
Detects underspecified areas in feature specs and records targeted clarification answers.
gkugaspeckit-plan
Generates implementation plans and design artifacts from feature specifications using the spec-kit planning workflow.
gkugaspeckit-analyze
Analyze spec.md, plan.md, and tasks.md for inconsistencies, gaps, and constitution violations.
gkugaspeckit-specify
Generate a feature specification from a natural language description within a spec-kit project.
gkugaspeckit-tasks
Generates a dependency-ordered tasks.md checklist from spec-kit design artifacts.
Frequently Asked Questions About Gaku Yasui
FAQPage SchemaWhat tasks can I perform with gkuga's spec-kit skills?▼
You can create feature specifications from natural language, clarify underspecified requirements, establish project constitutions, generate implementation plans and dependency-ordered tasks, execute those tasks, convert them into GitHub issues, produce custom checklists, and run cross-artifact consistency analysis.
Who should use these spec-kit command skills?▼
Software engineers and technical leads practicing specification-driven development benefit most. They suit developers who want structured feature lifecycles—spec, plan, tasks, implementation—with governance via project constitutions and quality gates via checklists and non-destructive artifact analysis.
What are the prerequisites for running these skills?▼
Every skill requires an existing spec-kit project structure containing a .specify/ directory. The skills are user-invocable commands sourced from github-spec-kit templates, so the spec-kit project scaffolding must be initialized before invoking specify, plan, tasks, or related commands.
How do the skills work together in a feature lifecycle?▼
Start with speckit-constitution to set principles, then speckit-specify to draft the spec, speckit-clarify to resolve gaps, speckit-plan for design artifacts, speckit-tasks for ordered tasks, speckit-analyze for consistency checks, speckit-implement for execution, and speckit-taskstoissues for GitHub tracking.
Are these skills open source and what do they cost?▼
The skills are derived from the github-spec-kit project's command templates, as recorded in each skill's metadata source field. They are distributed freely through the public repository with no licensing fee; users only need a compatible spec-kit project structure to invoke them.