القائمة
List and filter plan documents. Use when exploring plans, checking status, finding plans by module, or reviewing plan health.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | plan-list |
| description | List and filter plan documents. Use when exploring plans, checking status, finding plans by module, or reviewing plan health. |
| allowed-tools | Read, Bash(ls *) |
| context | fork |
| agent | design-doc-agent |
Lists and filters plan documents with flexible filtering and output options.
This skill lists plan documents by:
.claude/plans/List all plans:
/design-docs:plan-list
List by status:
/design-docs:plan-list --status=in-progress
List by module:
/design-docs:plan-list --module=effect-type-registry
Detailed view:
/design-docs:plan-list --format=detailed
--status: Filter by status (ready, in-progress, blocked, completed,
abandoned)--module: Filter by module name--owner: Filter by plan owner--format: Output format (summary, detailed, timeline) [default: summary]--sort: Sort field (created, updated, progress, status) [default: updated]--order: Sort order (asc, desc) [default: desc]--include-archived: Include archived plans from _archive/--stale: Show only stale plans (updated > 30 days)Scan for plan files:
.claude/plans/*.md.claude/plans/_archive/*.md_templates/)For each plan file:
Filter plans based on parameters:
Status Filter:
--status=in-progress--status=ready,in-progressModule Filter:
--module=effect-type-registrymodules arrayOwner Filter:
--owner=@spencerbeggsowner fieldStale Filter:
--stale: Show plans with updated > 30 days agoSort plans by specified field:
Sort Fields:
created: Plan creation dateupdated: Last update date (default)progress: Progress percentagestatus: Status value (alphabetical)name: Plan name (alphabetical)Sort Order:
desc: Newest/highest first (default)asc: Oldest/lowest firstThree output formats:
Summary (default):
Plans (5 active, 2 completed):
Active Plans:
📋 cache-optimization-plan [in-progress, 45%]
Updated: 2 days ago
Module: effect-type-registry
📋 observability-phase-2 [ready, 0%]
Updated: 1 day ago
Module: effect-type-registry
Completed Plans:
✅ design-linking-phase-1 [completed, 100%]
Completed: 3 days ago
Detailed:
Plan: cache-optimization-plan
Title: Cache Optimization Implementation
Status: in-progress (45%)
Module: effect-type-registry
Created: 2026-01-10 (8 days ago)
Updated: 2026-01-16 (2 days ago)
Started: 2026-01-11 (7 days ago)
Owner: @spencerbeggs
Estimated: 2-3 weeks
Implements: effect-type-registry/cache-optimization.md
Phases:
✓ Phase 1: Initial Implementation (100%)
→ Phase 2: Performance Testing (30%)
○ Phase 3: Documentation (0%)
Timeline:
Timeline View (sorted by started date):
Jan 10 ━━━━━━━━━━●━━━━━━━━━━ Jan 31
cache-optimization-plan [45%]
├─ Phase 1 (done)
├─ Phase 2 (active)
└─ Phase 3 (pending)
Jan 12 ━━━━━━━━━━━━━━━━━●━━━ Feb 05
observability-phase-2 [20%]
└─ Phase 1 (active)
Output listing results with:
/design-docs:plan-list
Shows all plans sorted by last update.
# Active plans only
/design-docs:plan-list --status=in-progress
# Multiple statuses
/design-docs:plan-list --status=ready,in-progress
/design-docs:plan-list --module=effect-type-registry
Shows only plans for specific module.
/design-docs:plan-list --stale
Shows plans not updated in 30+ days.
/design-docs:plan-list --format=detailed --status=in-progress
Shows full metadata for filtered plans.
/design-docs:plan-list --format=timeline --status=in-progress
Shows Gantt-style timeline of active plans.
/design-docs:plan-list --include-archived
Shows both active and archived plans.
/design-docs:plan-list --sort=progress --order=asc
Shows plans sorted by progress (lowest first).
/design-docs:plan-list --sort=created --order=desc
Shows newest plans first.
.claude/design/design.config.json.md files📋 - Active plan (ready, in-progress, blocked)✅ - Completed plan❌ - Abandoned plan⚠️ - Stale plan (warning)ready - Bluein-progress - Yellowblocked - Redcompleted - Greenabandoned - GrayProgress: [████████░░] 45%
No plans found matching filters
Filters:
Status: in-progress
Module: effect-type-registry
Suggestions:
1. Remove filters: /design-docs:plan-list
2. Create new plan: /design-docs:plan-create "My Feature"
3. Check archived plans: /design-docs:plan-list --include-archived
✗ Invalid status: {status}
Valid statuses:
- ready
- in-progress
- blocked
- completed
- abandoned
Fix: Use --status={valid-status}
✗ Module not found: {module}
Available modules:
- effect-type-registry
- rspress-plugin-api-extractor
- design-doc-system
Fix: Use --module={valid-module} or omit --module flag
✗ Plans directory not found: .claude/plans/
The plans directory doesn't exist yet.
Create it with:
mkdir -p .claude/plans
Or create your first plan:
/design-docs:plan-create "My First Plan"
The summary format includes statistics:
Plans: 12 total (7 active, 4 completed, 1 abandoned)
Status Breakdown:
Ready: 3 plans
In Progress: 4 plans
Blocked: 0 plans
Completed: 4 plans
Abandoned: 1 plan
Health:
Stale: 2 plans (updated > 30 days)
On Schedule: 5 plans
Behind: 2 plans
See examples.md for detailed usage examples.
design-docs:plan-validate - Validate plan structuredesign-docs:plan-create - Create new plansdesign-docs:plan-complete - Complete a plan and persist knowledge to design docsdesign-docs:plan-explore - Comprehensive plan explorationdesign-docs:design-index - Generate a design-doc table of contentsGenerate cross-reference graph showing relationships between design documents. Use when visualizing doc dependencies, finding related docs, or understanding documentation structure.
Validate design doc structure and frontmatter. Use when checking design docs for compliance, ensuring proper formatting, or verifying metadata before commits.
Comprehensive quality audit for CLAUDE.md context files. Use when performing thorough quality checks, preparing for releases, ensuring context efficiency, or verifying token optimization.
Style rules for LLM context files (CLAUDE.md, AGENTS.md and their .local variants). Fires automatically when these files are opened. Enforces on-demand loading patterns, proper @-reference syntax and lean context structure.
Split large CLAUDE.md into child files. Use when context files exceed word limits, are too verbose, or cover multiple distinct topics that should be separate.
Validate CLAUDE.md structure, formatting, and quality. Use when checking context files for compliance, ensuring proper structure, or verifying before commits.