Luan Dopke
Community@LuanDopke
Luan Dopke maintains 30 spec-kit skills for spec-driven development: feature specification, planning, task generation, implementation, and living-spec governance.
Agent Skills by Luan Dopke
Showing 25 vetted skills indexed across 1 GitHub repositories.
LuanDopkespeckit-checklist
Generate requirements-quality checklists for spec-kit feature specifications.
LuanDopkespeckit-companion-living-sync
Sync living specs with working-tree code changes grouped by capability.
LuanDopkespeckit-companion-after-specify
Writes the current spec-kit pipeline step into .spec-context.json for the Companion GUI.
LuanDopkespeckit-companion-specify
Generates prioritized feature specifications with user stories, requirements, and quality checklists.
LuanDopkespeckit-companion-tasks
Generates dependency-ordered task lists organized by user story for spec-kit projects.
LuanDopkespeckit-companion-mark-complete
Marks the active spec-kit feature as completed in .spec-context.json via the write-context.py script.
LuanDopkespeckit-constitution
Create or update the project constitution and sync dependent spec-kit templates.
LuanDopkespeckit-companion-after-implement
Records per-task implementation progress into .spec-context.json for the Companion GUI.
LuanDopkespeckit-implement
Executes implementation plans by processing tasks defined in tasks.md.
LuanDopkespeckit-converge
Assess codebase against spec-kit artifacts and append remaining work to tasks.md.
LuanDopkespeckit-companion-living-adopt
Drafts and registers living specs for existing code areas in spec-kit projects.
LuanDopkespeckit-taskstoissues
Convert spec-kit tasks into dependency-ordered GitHub issues with deduplication.
LuanDopkespeckit-clarify
Detects underspecified areas in feature specs and integrates clarification answers into the spec file.
LuanDopkespeckit-fixit-run
Diagnose and fix bugs by mapping them to spec-kit feature specifications.
LuanDopkespeckit-plan
Generates implementation plans and design artifacts from feature specifications using spec-kit templates.
LuanDopkespeckit-companion-plan
Generates implementation plans with research and design artifacts for spec-kit projects.
LuanDopkespeckit-companion-auto
Runs the full spec-kit pipeline from specify through mark-complete without pausing for approval.
LuanDopkespeckit-specify
Generate feature specifications from natural language descriptions using spec-kit templates.
LuanDopkespeckit-companion-living-move
Relocates living specs between central and colocated storage layouts in spec-kit projects.
LuanDopkespeckit-companion-doctor
Diagnose spec-kit run health by recomputing records, drift, and completion status.
LuanDopkespeckit-companion-resume
Resumes spec-driven pipelines by dispatching the next speckit command from recorded state.
LuanDopkespeckit-companion-after-plan
Records plan completion state into .spec-context.json for the SpecKit Companion GUI.
LuanDopkespeckit-companion-after-tasks
Records tasks completion state into .spec-context.json for the SpecKit Companion GUI.
LuanDopkespeckit-tasks
Generates dependency-ordered tasks.md checklists from spec-kit design artifacts.
Frequently Asked Questions About Luan Dopke
FAQPage SchemaWhat tasks can I perform using Luan Dopke's spec-kit skills?▼
You can create feature specifications from natural language, clarify underspecified areas with targeted questions, generate implementation plans and dependency-ordered tasks, execute tasks, convert tasks to GitHub issues, run cross-artifact consistency analysis, and manage living specs with drift, coverage, and sync reporting.
Who are these spec-kit skills designed for?▼
They target software engineers and teams practicing spec-driven development inside spec-kit projects. The Companion commands additionally serve developers who want GUI-visible pipeline state, change-size classification, resumable pipelines, and brownfield adoption of living specs for existing codebases.
What is required to run these skills?▼
Every skill requires an existing spec-kit project structure containing a .specify/ directory. Skills operate on spec-kit artifacts such as spec.md, plan.md, tasks.md, the project constitution, and the Companion's .spec-context.json state file; no other runtime dependencies are declared in the manifest.
How does the Companion pipeline execute end to end?▼
Run speckit-companion-auto for a hands-off specify, plan, tasks, implement, and mark-complete sequence, or step through individual Companion commands. speckit-companion-resume continues from the last completed step, while speckit-companion-status reports current step, decisions, and next action from .spec-context.json.
How do the living-spec skills keep documentation aligned with code?▼
living-sync groups working-tree changes by capability and updates affected specs in one pass; living-drift reports source files changed since each spec's last commit; living-coverage maps requirements to tests; living-adopt drafts [DRAFT] specs for named code areas; living-move relocates specs between central and colocated storage.