Assess scope change impact across project documentation and task lists.
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-change-spec
Please help me install this Agent Skill. Skill: gk-change-spec Source: https://github.com/gkganesh12/gk-stack/tree/main/skills-extra/gk-change-spec Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-change-spec
This skill prevents scope drift and architectural decay by enforcing a rigorous, documented workflow for any changes to project requirements during an active build.
Trigger the skill by stating your requirement change such as change add dark mode to the user interface.
High-intent search queries and answers about installing and using this skill.
Preventing scope drift involves pausing the agent to map the ripple effects of a new feature across the codebase and downstream dependencies. This generates necessary retrofit tasks before implementation begins.
Impact assessment for requirement changes automatically analyzes how a requested modification affects existing architecture, data models, and downstream dependencies. It pauses development to generate retrofit tasks before any code is written.
You do not need to update SPEC.md and TASKS.md manually when requirements evolve. The workflow enforces versioned documentation, ensuring these files are updated in lockstep with DECISIONS.md to maintain a perfect audit trail.
The best way to manage scope changes in AI-driven builds is to apply a strict documentation hierarchy using SPEC.md, PLAN.md, and DECISIONS.md. This ensures consistency by assessing impact across project documentation before implementation.
You can trigger a scope change assessment by stating your requirement change, such as requesting to add dark mode to the user interface. The system then automatically maps the architectural impact and generates retrofit tasks.
asm0deyGenerate dependency-ordered task lists from project plans into tasks.md files.
ruskibeatsAutomate architectural refactoring documentation and verification against a checklist.
julcasansMerge delta specifications into main project specs and archive completed changes.
santosomarCompare two requirements document versions and classify semantic changes.
