plan

Generate structured implementation plans for complex coding tasks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dostos/agent-workspace --skill plan-dostos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/dostos/agent-workspace/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/dostos/agent-workspace --skill plan-dostos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you craft clear, structured plans for complex tasks, breaking work into goals, requirements, scope, and validation to reduce ambiguity and save planning time.

Core Features & Use Cases

  • Structured planning: Generate comprehensive, implementable plans with sections for requirements, scope, files, data changes, and tests.
  • Plan lifecycle: Save, read, update, or delete plan files in $CODEX_HOME/plans to maintain a versioned playbook.
  • Use Case: When facing a complex coding migration, draft an implementation plan outlining steps, risks, and testing strategies, then save it as a markdown plan for team review.

Quick Start

Use the plan skill to draft a new plan for migrating a module. Then save it using the plan save workflow to ~/.codex/plans with the name you choose.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a structured plan for a complex coding task?

Generate a plan using this Skill to break down complex tasks into goals, requirements, scope, and validation steps. The plan is saved as markdown with frontmatter to ~/.codex/plans, reducing ambiguity and enabling team review.

What should a plan include for implementation tasks?

A structured plan covers requirements, scope, affected files, data changes, and testing strategies. This Skill enforces frontmatter fields and optional templates to ensure plans are comprehensive and implementable.

Can I save and version plans for team collaboration?

Yes. Plans are stored as markdown files in $CODEX_HOME/plans with create, read, update, and delete workflows, enabling versioned playbooks that teams can review and reference throughout a project.

How do I manage multiple plans across different projects?

This Skill manages the full plan lifecycle in a centralized directory. Use helper scripts like list_plans.py to browse, read_plan_frontmatter.py to inspect metadata, and create_plan.py to scaffold new plans quickly.

What's the best way to document a code migration strategy?

Draft an implementation plan outlining migration steps, risks, testing strategies, and validation criteria. Save it as a structured markdown plan to maintain a documented playbook for team execution and review.

Do I need special tools to read plan frontmatter metadata?

No. This Skill provides read-only repository context and helper scripts like read_plan_frontmatter.py to extract and inspect plan metadata without additional dependencies.