Update planning documents and coordinate code changes for bugs or requirement improvements.
npx skills add https://github.com/liqunx/wikiflow --skill wf-fix
Please help me install this Agent Skill. Skill: wf-fix Source: https://github.com/liqunx/wikiflow/tree/main/skills/wf-fix Command: npx skills add https://github.com/liqunx/wikiflow --skill wf-fix
When requirements evolve or bugs appear during WikiFlow development, the docs can drift from the actual implementation. wf-fix helps you correct that drift by updating the planning artifacts and recording the decisions that explain the “why”.
Run wf-fix with your change request so it automatically updates spec.md and tasks.md (and decisions.md if it’s a requirement improvement) after validating you are in the documentation repository.
High-intent search queries and answers about installing and using this skill.
To keep documentation and code synchronized during bug fixes, update planning artifacts like tasks.md to reflect the corrected behavior while routing code modifications strictly through the configured code repository path.
When requirements change, update spec.md to reflect the new behavior and append a structured entry to decisions.md to capture the rationale and impact, ensuring the documentation remains the source of truth.
The difference between updating documentation for a bug fix versus a requirement improvement is that bug fixes only require updating tasks.md, while requirement improvements require updating spec.md and logging the decision in decisions.md.
Yes, you can apply code changes and documentation updates using workflow fixes by validating the repository type first, keeping documentation files in the documentation repo, and directing code edits only through the configured paths.code.
You should use a documentation synchronization workflow for fixing development issues when active changes exist after an iterative development step and you need to correct drift between planning artifacts and actual implementation.
Documentation drifts from the actual implementation during iterative development because requirements evolve and bugs appear over time, requiring synchronized updates to planning artifacts and decision logs to maintain traceability.
liqunxGenerate spec.md and tasks.md from matched Wiki pages.
intent-integrity-chainGenerate domain-specific requirement quality checklists from spec.md, plan.md, and tasks.md.
GQAdonisCoordinate the PMPO lifecycle across AI tools with file-based state.
alvazoneCompare spec nodes against codebase implementation to identify drift.
