Skip to main content
kata-help Show available Kata skills, displaying the usage guide, explaining skill reference, or when the user asks for help with Kata. Triggers include "help", "show skills", "list skills", "what skills", "kata skills", and "usage guide".
Zur Installation springen Skills Marktplatz Entdecken und erkunden Sie KI-Skills, die von der Community erstellt wurden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Prompt-Details anzeigen Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
npx skills add https://github.com/gannonh/kata-skills --skill kata-helpDer Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.
Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.
ZIP herunterladen Herunterladen... Mehr aus diesem Repository Capture an idea, task, or issue that surfaces during a Kata session as a structured issue for later work. This skill creates markdown issue files in the .planning/issues/open directory with relevant metadata and content extracted from the conversation. Triggers include "add issue", "capture issue", "new issue", "create issue", "log issue", "file issue", "add todo" (deprecated), "capture todo" (deprecated), "new todo" (deprecated).
Add a milestone to an existing project, starting a new milestone cycle, creating the first milestone after project init, or defining what's next after completing work. Triggers include "add milestone", "new milestone", "start milestone", "create milestone", "first milestone", "next milestone", and "milestone cycle".
Add planned work discovered during execution to the end of the current milestone in the roadmap. This skill appends sequential phases to the current milestone's phase list, automatically calculating the next phase number. Triggers include "add phase", "append phase", "new phase", and "create phase". This skill updates ROADMAP.md and STATE.md accordingly.
SOC
Basierend auf der SOC-Berufsklassifikation
name kata-help description Show available Kata skills, displaying the usage guide, explaining skill reference, or when the user asks for help with Kata. Triggers include "help", "show skills", "list skills", "what skills", "kata skills", and "usage guide". metadata {"version":"0.1.0"}
Display the complete Kata skill reference with version info.
First, read the installed version:
if [ -n "$CLAUDE_PLUGIN_ROOT " ]; then
cat "$CLAUDE_PLUGIN_ROOT /VERSION" 2>/dev/null
else
echo "unknown"
fi
Then output the reference content below, inserting the version at the top. Do NOT add:
Project-specific analysis
Git status or file context
Next-step suggestions
Any commentary beyond the reference
# Kata Skill Reference
Version: {version from bash above}
Kata is a spec-driven development framework for Claude Code. It creates hierarchical project plans optimized for agentic development.
Quick Start
/kata-new-project - Initialize project (includes research, requirements, roadmap)/kata-plan-phase 1 - Create detailed plan for first phase/kata-execute-phase 1 - Execute the phase
Staying Updated Kata evolves fast. Check for updates periodically:
Shows what changed since your installed version and how to update.
Core Workflow /kata-new-project → /kata-plan-phase → /kata-execute-phase → repeat
Project Initialization /kata-new-project
One skill takes you from idea to ready-for-planning:
Deep questioning to understand what you're building
Optional domain research (spawns 4 parallel researcher agents)
Requirements definition with v1/v2/out-of-scope scoping
Roadmap creation with phase breakdown and success criteria
Creates all .planning/ artifacts:
PROJECT.md — vision and requirementsconfig.json — workflow mode (interactive/yolo)research/ — domain research (if selected)REQUIREMENTS.md — scoped requirements with REQ-IDsROADMAP.md — phases mapped to requirementsSTATE.md — project memory /kata-map-codebase
Analyzes codebase with parallel Explore agents
Creates .planning/codebase/ with 7 focused documents
Covers stack, architecture, structure, conventions, testing, integrations, concerns
Use before /kata-new-project on existing codebases
Usage: /kata-map-codebase
Phase Planning /kata-discuss-phase <number>
Captures how you imagine this phase working
Creates CONTEXT.md with your vision, essentials, and boundaries
Use when you have ideas about how something should look/feel
Usage: /kata-discuss-phase 2
/kata-research-phase <number>
Discovers standard stack, architecture patterns, pitfalls
Creates RESEARCH.md with "how experts build this" knowledge
Use for 3D, games, audio, shaders, ML, and other specialized domains
Goes beyond "which library" to ecosystem knowledge
Usage: /kata-research-phase 3
/kata-listing-phase-assumptions <number>
Shows Claude's intended approach for a phase
Lets you course-correct if Claude misunderstood your vision
No files created - conversational output only
Usage: /kata-listing-phase-assumptions 3
/kata-plan-phase <number>
Generates .planning/phases/pending/XX-phase-name/XX-YY-PLAN.md
Breaks phase into concrete, actionable tasks
Includes verification criteria and success measures
Multiple plans per phase supported (XX-01, XX-02, etc.)
Usage: /kata-plan-phase 1
Result: Creates .planning/phases/pending/01-foundation/01-01-PLAN.md
Execution /kata-execute-phase <phase-number>
Moves phase from pending/ → active/ → completed/
Groups plans by wave (from frontmatter), executes waves sequentially
Plans within each wave run in parallel via Task tool
Verifies phase goal after all plans complete
Updates REQUIREMENTS.md, ROADMAP.md, STATE.md
Usage: /kata-execute-phase 5
Quick Mode /kata-execute-quick-task
Quick mode uses the same system with a shorter path:
Spawns planner + executor (skips researcher, checker, verifier)
Quick tasks live in .planning/quick/ separate from planned phases
Updates STATE.md tracking (not ROADMAP.md)
Use when you know exactly what to do and the task is small enough to not need research or verification.
Usage: /kata-execute-quick-task
Result: Creates .planning/quick/NNN-slug/PLAN.md, .planning/quick/NNN-slug/SUMMARY.md
Roadmap Management /kata-add-phase <description>
Appends to ROADMAP.md
Uses next sequential number
Creates phase directory in pending/
Usage: /kata-add-phase "Add admin dashboard"
/kata-insert-phase <after> <description>
Creates intermediate phase (e.g., 7.1 between 7 and 8)
Useful for discovered work that must happen mid-milestone
Maintains phase ordering
Usage: /kata-insert-phase 7 "Fix critical auth bug"
Result: Creates Phase 7.1
/kata-remove-phase <number>
Deletes phase directory and all references
Renumbers all subsequent phases to close the gap
Only works on future (unstarted) phases
Git commit preserves historical record
Usage: /kata-remove-phase 17
Result: Phase 17 deleted, phases 18-20 become 17-19
/kata-move-phase <phase> <operation>
Cross-milestone: moves phase to target milestone, renumbers both
Reorder: changes phase position within milestone, renumbers all
Only pending phases can be moved
Usage: /kata-move-phase 3 to v1.6.0 (cross-milestone)
Usage: /kata-move-phase 3 before 1 (reorder within milestone)
Milestone Management /kata-add-milestone <name>
Deep questioning to understand what you're building next
Optional domain research (spawns 4 parallel researcher agents)
Requirements definition with scoping
Roadmap creation with phase breakdown
Mirrors /kata-new-project flow for brownfield projects (existing PROJECT.md).
Usage: /kata-add-milestone "v2.0 Features"
/kata-complete-milestone <version>
Creates MILESTONES.md entry with stats
Archives full details to milestones/ directory
Creates git tag for the release
Prepares workspace for next version
Usage: /kata-complete-milestone 1.0.0
Progress Tracking /kata-track-progress
Shows visual progress bar and completion percentage
Summarizes recent work from SUMMARY files
Displays current position and what's next
Lists key decisions and open issues
Offers to execute next plan or create it if missing
Detects 100% milestone completion
Usage: /kata-track-progress
Session Management /kata-resume-work
Reads STATE.md for project context
Shows current position and recent progress
Offers next actions based on project state
/kata-pause-work
Creates .continue-here file with current state
Updates STATE.md session continuity section
Captures in-progress work context
Debugging /kata-debug [issue description]
Gathers symptoms through adaptive questioning
Creates .planning/debug/[slug].md to track investigation
Investigates using scientific method (evidence → hypothesis → test)
Survives /clear — run /kata-debug with no args to resume
Archives resolved issues to .planning/debug/resolved/
Usage: /kata-debug "login button doesn't work"
Usage: /kata-debug (resume active session)
Issue Management /kata-add-issue [description]
Extracts context from conversation (or uses provided description)
Creates structured issue file in .planning/issues/open/
Infers area from file paths for grouping
Checks for duplicates before creating
Updates STATE.md issue count
Usage: /kata-add-issue (infers from conversation)
Usage: /kata-add-issue Add auth token refresh
/kata-check-issues [area]
Lists all pending issues with title, area, age
Optional area filter (e.g., /kata-check-issues api)
Loads full context for selected issue
Routes to appropriate action (work now, add to phase, brainstorm)
Moves issue to done/ when work begins
Usage: /kata-check-issues
Usage: /kata-check-issues api
User Acceptance Testing /kata-verify-work [phase]
Extracts testable deliverables from SUMMARY.md files
Presents tests one at a time (yes/no responses)
Automatically diagnoses failures and creates fix plans
Ready for re-execution if issues found
Usage: /kata-verify-work 3
Milestone Auditing /kata-audit-milestone [version]
Reads all phase VERIFICATION.md files
Checks requirements coverage
Spawns integration checker for cross-phase wiring
Creates MILESTONE-AUDIT.md with gaps and tech debt
Usage: /kata-audit-milestone
/kata-plan-milestone-gaps
Reads MILESTONE-AUDIT.md and groups gaps into phases
Prioritizes by requirement priority (must/should/nice)
Adds gap closure phases to ROADMAP.md
Ready for /kata-plan-phase on new phases
Usage: /kata-plan-milestone-gaps
Configuration /kata-customize
List all customizable templates with override status
Copy a default template for local editing
Edit an override with conversational changes
Validate overrides against required schemas
Usage: /kata-customize
Usage: /kata-customize list
Usage: /kata-customize copy summary-template.md
Usage: /kata-customize validate
/kata-configure-settings
Toggle researcher, plan checker, verifier agents
Select model profile (quality/balanced/budget)
Updates .planning/config.json
Usage: /kata-configure-settings
/kata-set-profile <profile>
quality — Opus everywhere except verificationbalanced — Opus for planning, Sonnet for execution (default)budget — Sonnet for writing, Haiku for research/verification Usage: /kata-set-profile budget
Utility Skills /kata-help
/kata-whats-new
Shows installed vs latest version comparison
Displays changelog entries for versions you've missed
Highlights breaking changes
Provides update instructions when behind
Files & Structure .planning/
├── PROJECT.md # Project vision
├── REQUIREMENTS.md # Scoped requirements with REQ-IDs
├── ROADMAP.md # Current phase breakdown
├── STATE.md # Project memory & context
├── MILESTONES.md # Completed milestone history
├── config.json # Workflow mode & gates
├── templates/ # Template overrides (customized output formats)
├── research/ # Domain research (from project init)
├── issues/ # Captured ideas and tasks
│ ├── open/ # Issues waiting to be worked on
│ └── done/ # Completed issues
├── debug/ # Active debug sessions
│ └── resolved/ # Archived resolved issues
├── codebase/ # Codebase map (brownfield projects)
│ ├── STACK.md # Languages, frameworks, dependencies
│ ├── ARCHITECTURE.md # Patterns, layers, data flow
│ ├── STRUCTURE.md # Directory layout, key files
│ ├── CONVENTIONS.md # Coding standards, naming
│ ├── TESTING.md # Test setup, patterns
│ ├── INTEGRATIONS.md # External services, APIs
│ └── CONCERNS.md # Tech debt, known issues
├── milestones/ # Archived milestone details
├── quick/ # Quick task plans and summaries
│ └── NNN-slug/
│ ├── PLAN.md
│ └── SUMMARY.md
└── phases/
├── pending/ # Phases not yet started
│ └── 03-next-phase/
│ └── 03-01-PLAN.md
├── active/ # Phase currently being executed
│ └── 02-in-progress/
│ ├── 02-01-PLAN.md
│ └── 02-01-SUMMARY.md
└── completed/ # Finished phases
└── 01-foundation/
├── 01-01-PLAN.md
└── 01-01-SUMMARY.md
Workflow Modes Set during /kata-new-project:
Confirms each major decision
Pauses at checkpoints for approval
More guidance throughout
Auto-approves most decisions
Executes plans without confirmation
Only stops for critical checkpoints
Change anytime by editing .planning/config.json
Planning Configuration Configure how planning artifacts are managed in .planning/config.json:
planning.commit_docstrue)
true: Planning artifacts committed to git (standard workflow)false: Planning artifacts kept local-only, not committed
Add .planning/ to your .gitignore
Useful for OSS contributions, client projects, or keeping planning private
All planning files still work normally, just not tracked in git
planning.search_gitignoredfalse)
true: Add --no-ignore to broad ripgrep searchesOnly needed when .planning/ is gitignored and you want project-wide searches to include it
{
"planning" : {
"commit_docs" : false ,
"search_gitignored" : true }
}
Common Workflows /kata-new-project # Unified flow: questioning → research → requirements → roadmap
/clear
/kata-plan-phase 1 # Create plans for first phase
/clear
/kata-execute-phase 1 # Execute all plans in phase
Resuming work after a break:
/kata-track-progress # See where you left off and continue
Adding urgent mid-milestone work:
/kata-insert-phase 5 "Critical security fix"
/kata-plan-phase 5.1
/kata-execute-phase 5.1
/kata-complete-milestone 1.0.0
/clear
/kata-add-milestone # Start next milestone (questioning → research → requirements → roadmap)
Capturing ideas during work:
/kata-add-issue # Capture from conversation context
/kata-add-issue Fix modal z-index # Capture with explicit description
/kata-check-issues # Review and work on issues
/kata-check-issues api # Filter by area
/kata-debug "form submission fails silently" # Start debug session
# ... investigation happens, context fills up ...
/clear
/kata-debug # Resume from where you left off
Getting Help
Read .planning/PROJECT.md for project vision
Read .planning/STATE.md for current context
Check .planning/ROADMAP.md for phase status
Run /kata-track-progress to check where you're up to
