story-remediation

To fix broken file references and missing frontmatter in story files, you need an automated remediation process that classifies audit findings and applies deterministic fixes to correct file paths and restore metadata. This Skill automates that correction workflow using a structured audit file.

Story and epic audit remediation is the process of resolving validation findings related to broken file references, stale status labels, and context path errors. It classifies issues to apply automated fixes or guide interactive resolutions to maintain code quality.

You can resolve stale status labels and context file path errors by running an automated remediation tool with the audit results file. It directly addresses these findings by applying safe fixes or guiding you through interactive resolution steps.

Yes, you can automatically apply fixes for safe, deterministic issues like broken file references listed in an audit report. For complex findings, the remediation process provides guided interactive resolutions with clear options and confirmations.

Yes, you need a structured audit file detailing findings and remediation steps to automate the correction of story and epic files. The remediation process relies on this input to classify issues and verify applied changes across project files.

Automated story file remediation is limited to safe, deterministic fixes for common issues like broken references. Complex findings cannot be fully automated and require guided interactive resolutions with manual confirmation to ensure correct changes.