Reconcile FE design documents and tasks.json from change-analyzer outputs and feedback.
npx skills add https://github.com/rachel353/fullty-plan --skill change-doc
Please help me install this Agent Skill. Skill: change-doc Source: https://github.com/rachel353/fullty-plan/tree/main/.claude/skills/change-doc Command: npx skills add https://github.com/rachel353/fullty-plan --skill change-doc
FE documentation often drifts after change-analyzer outcomes and planning feedback, leading to inconsistent specifications across conceptual_model, ia_structure, user_stories, logical_architecture, and tasks.json. This Skill automatically reconciles and restores alignment by applying authoritative changes from docs/changes and feedback to dependent documents.
Apply the latest change-analyzer results or planning feedback to update and synchronize all related FE documentation (conceptual_model, ia_structure, user_stories, logical_architecture, and tasks.json).
High-intent search queries and answers about installing and using this skill.
Documentation synchronization applies planning feedback to update tasks.json and markdown files simultaneously. It ensures dependent documents like conceptual_model and ia_structure reflect the same state by reading authoritative changes and reconciling discrepancies.
Design documents drift when change-analyzer outcomes and planning feedback are applied without updating dependent files. Reconciliation restores alignment by propagating authoritative changes from docs/changes across user_stories and logical_architecture.
You can automatically update conceptual_model and ia_structure, but no automated commits occur without user approval. The system validates changes safely and requires your approval before finalizing any document synchronization.
The reconciliation process records all applied changes in docs/changes to maintain a traceable change log. This audit trail captures updates made across conceptual_model, ia_structure, user_stories, logical_architecture, and tasks.json.
Document reconciliation is needed whenever docs/changes indicate a discrepancy or when planning feedback requests alignment. Running it restores consistency across conceptual_model, ia_structure, user_stories, logical_architecture, and tasks.json.
rachel353Compile feature scope and execution plans from project docs into a markdown file.
thurstonsandAnalyze commits since divergence and draft editable pull request descriptions.
0xHoneyJarValidate sprint implementations against acceptance criteria and quality standards.
tsuna44Convert Excel USDM change specifications into synchronized Markdown documents.
