From iterate
Compare specs with implementation state, update spec status, and generate sync reports. Use when syncing specs, checking implementation status, marking tasks complete, generating sync reports, or when user mentions spec sync, status updates, or implementation tracking.
How this skill is triggered — by the user, by Claude, or both
Slash command
/iterate:sync-patternsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reusable patterns and scripts for syncing specification documents with implementation state. This skill provides tools to compare what's documented in specs vs what's implemented in code, update spec status markers, identify completed tasks, and generate comprehensive sync reports.
examples/ci-cd-integration.mdexamples/status-markers.mdexamples/sync-workflow.mdscripts/compare-specs-vs-code.shscripts/find-completed-tasks.shscripts/generate-sync-report.shscripts/update-feature-status.shscripts/update-spec-status.shtemplates/discrepancy-report.template.mdtemplates/spec-frontmatter.template.mdtemplates/spec-status-update.template.mdtemplates/sync-report.template.mdtemplates/task-list.template.mdReusable patterns and scripts for syncing specification documents with implementation state. This skill provides tools to compare what's documented in specs vs what's implemented in code, update spec status markers, identify completed tasks, and generate comprehensive sync reports.
Use this skill when:
Script: scripts/compare-specs-vs-code.sh
Compares specification requirements against actual code implementation.
Usage:
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/iterate/skills/sync-patterns/scripts/compare-specs-vs-code.sh <spec-file> [code-directory]
What it does:
Returns:
Script: scripts/update-spec-status.sh
Updates status markers in specification documents.
Usage:
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/iterate/skills/sync-patterns/scripts/update-spec-status.sh <spec-file> <status>
Supported statuses:
complete - Mark entire spec as completedin-progress - Mark spec as currently being worked onpending - Mark spec as not yet startedblocked - Mark spec as blocked (requires reason)What it does:
Script: scripts/find-completed-tasks.sh
Identifies tasks that are completed in code but not marked complete in specs.
Usage:
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/iterate/skills/sync-patterns/scripts/find-completed-tasks.sh [spec-directory] [code-directory]
What it does:
Completion evidence includes:
Script: scripts/generate-sync-report.sh
Creates comprehensive sync report for entire project or specific spec.
Usage:
bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/iterate/skills/sync-patterns/scripts/generate-sync-report.sh [spec-file-or-directory] [output-file]
Report includes:
Output formats:
--format=json)--format=html)Location: templates/spec-status-update.template.md
Template for updating spec status with proper formatting and metadata.
Variables:
{{SPEC_NAME}} - Name of specification{{STATUS}} - New status (complete/in-progress/pending/blocked){{TIMESTAMP}} - ISO 8601 timestamp{{REASON}} - Reason for status change (optional){{UPDATED_BY}} - Who updated (agent/user name)Location: templates/sync-report.template.md
Template for comprehensive sync reports.
Variables:
{{PROJECT_NAME}} - Project name{{REPORT_DATE}} - Report generation date{{SYNC_PERCENTAGE}} - Overall sync percentage{{COMPLETED_COUNT}} - Number of completed items{{IN_PROGRESS_COUNT}} - Number of in-progress items{{PENDING_COUNT}} - Number of pending items{{COMPLETED_ITEMS}} - List of completed items{{IN_PROGRESS_ITEMS}} - List of in-progress items{{PENDING_ITEMS}} - List of pending items{{DISCREPANCIES}} - List of discrepancies{{RECOMMENDATIONS}} - Next stepsSee examples/sync-workflow.md for step-by-step guide on performing a complete sync.
High-level steps:
See examples/status-markers.md for examples of completion markers in code.
Common markers:
describe('feature'), it('should work')The sync-analyzer agent uses these scripts to:
Example agent usage:
Phase 1: Analyze Sync State
Run comparison script:
Bash: bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/iterate/skills/sync-patterns/scripts/compare-specs-vs-code.sh specs/feature.md src/
Phase 2: Update Status
Mark completed items:
Bash: bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/iterate/skills/sync-patterns/scripts/update-spec-status.sh specs/feature.md complete
Phase 3: Generate Report
Create sync report:
Bash: bash ~/.claude/plugins/marketplaces/dev-lifecycle-marketplace/plugins/iterate/skills/sync-patterns/scripts/generate-sync-report.sh specs/ sync-report.md
Always timestamp status changes
Validate status transitions
Document blocking reasons
Regular syncs
Automated triggers
Share with team
Track over time
All scripts implement consistent error handling:
# Exit codes
0 - Success
1 - Invalid arguments
2 - File not found
3 - Invalid status
4 - Parsing error
5 - Write permission error
Error output:
Required:
Optional (enhanced features):
Basic usage: Use scripts directly for simple tasks
Advanced usage: Chain scripts together for complex workflows
Full integration: Integrate with agents and commands for automated syncing
Location: plugins/iterate/skills/sync-patterns/
Used by: sync-analyzer agent, /iterate:sync command
Dependencies: Bash, standard UNIX tools
npx claudepluginhub vanman2024/dev-lifecycle-marketplace --plugin iterateMaps intended features (docs, specs, JIRA, GitHub issues) to implementation state, detecting NOT_STARTED, IN_PROGRESS, IMPLEMENTED, DRIFTED, or ABANDONED statuses. Use during discovery or via /fp:check.
Transforms ideas into structured specifications (requirements, design, tasks) before implementation. Use when building features, fixing bugs, refactoring, or designing systems.
Write and manage spec files with search, conflict detection, and reporting. Use when user asks to create a spec, update a spec, write a spec, or mentions 스펙 생성, 스펙 업데이트, 스펙 작성, 스펙 만들어줘. Proactively trigger whenever the user's request involves specification documents, even if they don't explicitly say "spec".