Synchronize keel documentation with implementation progress and detect doc-code drift.
npx skills add https://github.com/ab300819/keel-workflow --skill sync-ab300819
Please help me install this Agent Skill. Skill: sync Source: https://github.com/ab300819/keel-workflow/tree/main/skills/sync Command: npx skills add https://github.com/ab300819/keel-workflow --skill sync-ab300819
archive/ files with cascade support and an index, triggered by line-count or completion thresholds. - PRD Back-Propagation: Reverse-syncs keel requirement changes to the PRD mapping table via --back-propagate-prd. - Use Case: After finishing a sprint's development tasks, run the sync command to update task statuses, verify traceability coverage, get a health score, and archive completed features. ## Quick Start Ask the AI to run /sync after completing development tasks to update keel document statuses and generate a deviation report.High-intent search queries and answers about installing and using this skill.
Run /sync with no arguments to execute the default trace → audit → check pipeline. It scans the workspace state, compares it against keel documents, auto-absorbs low-risk status updates, and asks for confirmation before writing high-risk changes.
Use /sync --archive with an optional document type (requirements, design, tests, tasks). Archiving triggers when thresholds are met, such as more than 15 completed tasks or documents exceeding line limits, and supports cascading archival of related content.
No. The trace phase deliberately does not scan code for keel numbering annotations. It validates the traceability matrix's change-source column, which records repository@sha references written by dev-workflow commits, keeping the dependency direction docs-to-code only.
Sync updates document statuses and absorbs deviations based on implementation progress, while verify checks implementation correctness and alignment. Schema drift diagnosis is delegated to /verify --schema-drift, and sync only merges its results into the health report.
Features belonging to a milestone that has not passed manual acceptance verification are not archived, even if marked complete. Archiving them would remove the F-to-milestone mapping needed as evidence during milestone acceptance.
iJosueehImplements DEV-PLAN phases one at a time with TDD, sub-agent isolation, and four-step verification.
chapmanjwAnalyze Minecraft build logs and documentation to extract process improvements.
minhquan2904Align OpenSpec change documentation with current source code and report drift.
thistleknotRun a Red-Green-Refactor TDD lifecycle with executable assertions and anti-tampering checks.