From spec-kit
Generate technical implementation plans from feature specifications. Use after creating a spec to define architecture, tech stack, and implementation phases. Creates plan.md with detailed technical design.
npx claudepluginhub clockwork-temptation/plugin_01uphfxag16yzb4yodkyf1rzThis skill uses the workspace's default tool permissions.
```text
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Check for extension hooks (before planning):
.specify/extensions.yml exists in the project root.hooks.before_plan keyenabled is explicitly false. Treat hooks without an enabled field as enabled by default.condition expressions:
condition field, or it is null/empty, treat the hook as executablecondition, skip the hook and leave condition evaluation to the HookExecutor implementationoptional flag:
optional: true):
## Extension Hooks
**Optional Pre-Hook**: {extension}
Command: `/{command}`
Description: {description}
Prompt: {prompt}
To execute: `/{command}`
optional: false):
## Extension Hooks
**Automatic Pre-Hook**: {extension}
Executing: `/{command}`
EXECUTE_COMMAND: {command}
Wait for the result of the hook command before proceeding to the Outline.
.specify/extensions.yml does not exist, skip silentlyspec.md as the healed source of truth. If the workflow already repaired the spec in-session, plan from the repaired artifact instead of stale prompt text or earlier snapshots.spec.md, .specify/memory/constitution.md, repository context, or traceable research.plan.md around broken requirements.agents/, hooks/hooks.json, .mcp.json, .lsp.json, output-styles/, settings.json, or src/cowork/, also read docs/cowork/asset-map.md and docs/cowork/operating-mode.md before finalizing architecture decisions.skills/spec-kit-plan/references/ are reference mirrors for understanding behavior. Actual execution must target the live scripts under .specify/scripts/powershell/.agents/research-orchestrator.mdagents/plan-gap-closer.mddocs/cowork/asset-map.mddocs/cowork/operating-mode.mdskills/spec-kit-tasks/SKILL.mdskills/spec-kit-setup-runtime/SKILL.mdSetup: Run .specify/scripts/powershell/setup-plan.ps1 -Json from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
Load context: Read FEATURE_SPEC and .specify/memory/constitution.md. Load IMPL_PLAN template (already copied).
Execute plan workflow: Follow the structure in IMPL_PLAN template to:
docs/cowork/asset-map.md and docs/cowork/operating-mode.mdtasks.md as the later execution authority: plan outputs must prepare /speckit.tasks, not override or bypass itStop and report: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
Check for extension hooks: After reporting, check if .specify/extensions.yml exists in the project root.
hooks.after_plan keyenabled is explicitly false. Treat hooks without an enabled field as enabled by default.condition expressions:
condition field, or it is null/empty, treat the hook as executablecondition, skip the hook and leave condition evaluation to the HookExecutor implementationoptional flag:
optional: true):
## Extension Hooks
**Optional Hook**: {extension}
Command: `/{command}`
Description: {description}
Prompt: {prompt}
To execute: `/{command}`
optional: false):
## Extension Hooks
**Automatic Hook**: {extension}
Executing: `/{command}`
EXECUTE_COMMAND: {command}
.specify/extensions.yml does not exist, skip silentlyExtract unknowns from Technical Context above:
Generate and dispatch research agents:
For each unknown in Technical Context:
Task: "Research {unknown} for {feature context}"
For each technology choice:
Task: "Find best practices for {tech} in {domain}"
Consolidate findings in research.md using format:
Output: research.md with all NEEDS CLARIFICATION resolved
Prerequisites: research.md complete
Extract entities from feature spec → data-model.md:
Define interface contracts (if project has external interfaces) → /contracts/:
Agent context update:
.specify/scripts/powershell/update-agent-context.ps1 -AgentType claudeOutput: data-model.md, /contracts/*, quickstart.md, agent-specific file
/speckit.tasks can consume them without additional user promptingskills/spec-kit-setup-runtime/SKILL.md before treating the repository as ready for downstream execution