Plan Complete

Dry run (preview changes):

/plan-complete subagent-integration --dry-run

Parameters

Required

• plan-name: Plan identifier (without .md extension)

Optional

• --outcome: Completion outcome (success, partial, failed) [default: success]
• --dry-run: Preview changes without executing
• --keep: Keep plan file after completion (for reference)

Workflow

High-level completion process:

1. Load plan from .claude/plans/{plan-name}.md
2. Validate completion requirements (status, progress, linked docs exist)
3. Update design docs (status, last-synced, completion metadata)
4. Record completion in design doc frontmatter
5. Delete plan file (unless --keep specified)
6. Generate report of all actions taken

For detailed implementation steps, see supporting documentation below.

Supporting Documentation

When you need detailed information, load the appropriate supporting file:

For Completion Workflow

See instructions.md for:

• Step-by-step completion process
• Design doc update procedures
• Completion metadata format
• Validation requirements
• Error handling and rollback

Load when: Performing completion or need implementation details

For Design Doc Updates

See design-doc-updates.md for:

• Updating status (draft → current, stub → current)
• Recording completion metadata format
• Handling multiple linked design docs
• Last-synced timestamp updates
• Bidirectional link cleanup

Load when: Working with design doc updates or metadata

For Usage Examples

See examples.md for:

• Complete successful implementation
• Partial completion with notes
• Failed implementation (knowledge still valuable)
• Multiple design docs linked
• Dry run preview
• Keep plan file for reference

Load when: User needs examples or clarification

Validation Requirements

Before completion, the skill verifies:

Plan Requirements

• ✅ Plan file exists
• ✅ Status is "completed" or can be set to completed
• ✅ Progress is 100%
• ✅ All required frontmatter fields present
• ✅ Has implements field with design docs

Design Doc Requirements

• ✅ All linked design docs exist
• ✅ Design docs are in appropriate state (draft/stub)
• ✅ Bidirectional links are correct

Implementation Evidence

• ✅ Design docs have been updated with implementation details
• ✅ Last-synced is reasonably recent (< 30 days)
• ✅ Completeness score increased during implementation

What Gets Updated

Design Doc Frontmatter