plan

Name: plan
Availability: InStock
Author: AsiaOstrich

Generate plan.json files from specifications, OpenSpec changes, or free-text requirements.

6|1|Updated Mar 4, 2026

Search Tags:#automation #planning #spec #plan #openspec #task #devap

Ready to run

npx skills add https://github.com/AsiaOstrich/dev-autopilot --skill plan-asiaostrich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/AsiaOstrich/dev-autopilot/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/AsiaOstrich/dev-autopilot --skill plan-asiaostrich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert specifications, OpenSpec changes, or free-text requirements into ready-to-run plan.json files for the devap workflow, saving time and reducing manual coordination.

Core Features & Use Cases

Generate plan.json from a spec md (SPEC-001 style) or an OpenSpec changes directory.
Support interactive or script-driven planning, with multiple input modes (text, file, or directory).
Use cases include turning a product requirement spec into a task plan, integrating with a DAG orchestrator, and validating plans before execution.

Quick Start

Use /plan <spec-file.md> to generate a plan.json from your specification.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I convert a product spec into a structured task plan?▼

To convert a product spec into a structured task plan, use this Skill to parse specification md files or free-text requirements and generate a ready-to-run plan.json file. It implements multi-input parsing and phase-based task generation for the devap workflow.

Can I generate plan.json directly from an OpenSpec changes directory?▼

Yes, you can generate plan.json directly from an OpenSpec changes directory. The Skill supports multiple input modes including directory parsing, allowing you to turn OpenSpec changes into structured task plans instantly without manual coordination.

What is the best way to automate task planning for Claude Code workflows?▼

The best way to automate task planning for Claude Code workflows is to use this Skill to transform specifications or free-text requirements into validated plan.json files. It produces ready-to-run plans through multi-input parsing and phase-based task generation.

Does this spec-to-plan conversion tool support interactive planning?▼

Yes, this spec-to-plan conversion tool supports both interactive and script-driven planning. You can use multiple input modes such as text, file, or directory specifications to generate and validate your plan.json before execution.

How do I validate a plan before execution in a DAG orchestrator?▼

To validate a plan before execution in a DAG orchestrator, this Skill implements plan validation during generation from your specifications or OpenSpec changes. It ensures the output plan.json is structured, ready-to-run, and correctly formatted for downstream execution.

What input formats are supported for generating task plans?▼

Supported input formats for generating task plans include SPEC-001 style spec md files, OpenSpec changes directories, and free-text requirements. The Skill parses these inputs to automatically produce structured plan.json files for your project.