speckit-fixit-run

Diagnose and fix bugs by mapping them to spec-kit feature specifications.

1|Updated Nov 21, 2020
One-click install
npx skills add https://github.com/LuanDopke/persefone --skill speckit-fixit-run-luandopke
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-fixit-run
Source: https://github.com/LuanDopke/persefone/tree/main/.agents/skills/speckit-fixit-run
Command: npx skills add https://github.com/LuanDopke/persefone --skill speckit-fixit-run-luandopke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging without context often leads to fixes that violate intended behavior. This Skill grounds bug fixes in the feature specification, ensuring code changes match what the spec says the code should do. ## Core Features & Use Cases - Spec-Aware Bug Mapping: Loads spec.md, tasks.md, and constitution.md to map a natural-language bug description to the relevant user story, functional requirement, or acceptance criterion. - Plan-Then-Act Workflow: Presents a proposed fix plan with root cause analysis and waits for explicit user approval before modifying any code. - Guardrails and Escalation: Warns on scope creep (more than 4 files), flags spec conflicts, and hard-blocks fixes that violate constitution principles. - Use Case: A user reports "login link email never arrives in dev mode." The Skill maps the bug to the authentication user story in spec.md, locates the email backend code referenced in completed tasks, proposes a minimal fix, and applies it after approval. ## Quick Start Run /speckit.fixit.run followed by a natural-language description of the bug you want fixed, such as "/speckit.fixit.run the plant list returns duplicates after filtering".

Frequently Asked Questions about speckit-fixit-run

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a bug with spec-kit using natural language?▼

Run /speckit.fixit.run followed by a bug description. The Skill loads the feature spec, maps the bug to user stories and requirements, proposes a fix plan, and applies the minimal change only after you approve it.

What project structure does spec-aware bug fixing require?▼

It requires a spec-kit project with a .specify directory, a specs/ folder containing feature directories, and at minimum spec.md and tasks.md for the active feature. You must also be on a feature branch or select a feature when prompted.

Can the fix command modify spec.md or tasks.md?▼

No. The Skill never modifies spec artifacts such as spec.md, plan.md, tasks.md, or constitution.md. It treats the specification as the read-only source of truth for intended behavior and only changes implementation code.

Why does the bug fix stop with a constitution violation error?▼

Constitution violations are hard blocks. If the proposed fix would violate a MUST principle in constitution.md, the Skill outputs the plan for transparency but refuses to proceed until the constitution is updated separately or an alternative approach is found.

What happens if no completed tasks exist in tasks.md?▼

The Skill aborts with an error stating there is no implementation to debug. You must run /speckit.implement first so that completed tasks exist to reference when locating affected source files.