spec-driven-remediation
Automates remediation of story and context files based on validation audit data.
Install
mkdir -p .claude/skills/spec-driven-remediation && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13603" && unzip -o skill.zip -d .claude/skills/spec-driven-remediation && rm skill.zipInstalls to .claude/skills/spec-driven-remediation
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Apply automated and guided fixes to story, epic, and context files based on structured audit findings with 4-layer anti-skip enforcement. Classifies findings by fix complexity, applies safe automated fixes, guides interactive fixes with user confirmation, verifies all changes, and produces a fix report. Uses Execute-Verify-Record pattern at every step to prevent token optimization bias. Use when /fix-story is invoked, when audit findings need remediation, or when custody chain validation produces findings requiring correction. Make sure to use this skill whenever the user mentions fixing stories, remediating audit findings, applying fixes from /validate-stories output, or addressing custody chain violations.Key capabilities
- →Apply automated fixes to story, epic, and context files
- →Guide interactive fixes with user confirmation
- →Verify all changes using an Execute-Verify-Record pattern
- →Produce a fix report summarizing applied changes
- →Classify findings by fix complexity
How it works
The skill applies automated and guided fixes to story, epic, and context files based on audit findings. It uses an Execute-Verify-Record pattern at every step, ensures user approval for structural changes, and produces a fix report.
Inputs & outputs
When to use spec-driven-remediation
- →Fixing story files
- →Remediating audit findings
- →Correcting custody chain violations
- →Applying validation fixes
About spec-driven-remediation
Uses an Execute-Verify-Record model to apply fixes to story and epic files. It ensures all changes are verified and require user approval for structural modifications.
>
When not to use it
- →When the user does not mention fixing stories, remediating audit findings, or addressing custody chain violations
- →When ambiguous or conflicts are detected, requiring user intervention
- →When the `devforgeai-validate` CLI is not installed
Limitations
- →User approval gates every structural change
- →If ambiguous or conflicts detected: HALT and use ask the user
- →No files modified without user approval (--dry-run respected)
How it compares
This skill automates the remediation of audit findings in story and epic files with a strict Execute-Verify-Record pattern and user approval gates, providing a verifiable and controlled fix process compared to manual, unverified changes.
Compared to similar skills
spec-driven-remediation side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| spec-driven-remediation (this skill) | 0 | 1mo | Review | Advanced |
| feature-workflow | 0 | 3mo | No flags | Intermediate |
| development workflow | 0 | 6mo | No flags | Intermediate |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by bankielewicz
View all by bankielewicz →You might also like
feature-workflow
npomfret
Use PROACTIVELY for non-trivial features, bug fixes, behavior changes, or refactors so work starts with discovery, readiness refactoring, approved-pattern selection, and verification planning before implementation.
development workflow
rcarmo
workflow patterns for planning, subagents, self-improvement, and verification
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
claude-automation-recommender
anthropics
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
codex-skill
feiskyer
Use when user asks to leverage codex, gpt-5, or gpt-5.1 to implement something (usually implement a plan or feature designed by Claude). Provides non-interactive automation mode for hands-off task execution without approval prompts.
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.