skills.rest
progremir
progremirCOMMUNITY
Explore all skills by this author →
Website𝕏@progremirGitHub

plan

Generate OpenSpec planning artifacts from an understand.md input.

Updated Feb 23, 2026
Search Tags:#design#planning#development#artifacts#openspec#stories#specs
One-click install
npx skills add https://github.com/progremir/pluto --skill plan-progremir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/progremir/pluto/tree/main/skills/plan
Command: npx skills add https://github.com/progremir/pluto --skill plan-progremir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of essential planning artifacts, streamlining the software development lifecycle from understanding requirements to defining executable stories.

Core Features & Use Cases

  • OpenSpec DAG Adherence: Ensures artifacts are created in the correct dependency order (understand → proposal → specs + design → stories).
  • Automated Artifact Generation: Creates proposal.md, specs/, design.md, and stories.json based on input understanding.
  • Use Case: After gathering requirements for a new feature, use this Skill to automatically generate a detailed technical proposal, a set of testable specifications, a comprehensive design document, and a breakdown of user stories ready for development.

Quick Start

Use the plan skill to generate planning artifacts based on the understanding document.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate software planning artifacts like specifications and user stories?▼

Planning artifacts follow the OpenSpec DAG dependency order: understand leads to proposal, which generates specs and design, finally breaking down into executable stories.

What is the OpenSpec DAG dependency order for creating design documents and specs?▼

The OpenSpec DAG enforces a specific creation sequence: understand → proposal → specs + design → stories. This ensures structured software development by generating dependencies in the correct order.

How do I create user stories with acceptance criteria from a requirements document?▼

You create user stories by feeding requirements into an `understand.md` file. The Skill generates a `stories.json` file while enforcing specific rules for story size, dependency order, and acceptance criteria.

What input format is required to automatically generate a technical proposal and design document?▼

The required input format is an `understand.md` file. Based on this input understanding, the Skill automatically generates a detailed technical proposal and a comprehensive `design.md` document.

Can I generate testable specifications alongside user stories for software development?▼

Yes, you can generate testable specifications alongside user stories. The Skill creates a `specs/` directory containing testable specifications and a `stories.json` file ready for development.

Related Skills

Explore More Software Engineering Skills→
PiaoxuemoliPiaoxuemoli

plan

Generate markdown planning documents from user input without execution.

Community
Basic
qodex-aiqodex-ai
39

specification-executor

Transforms workspace specification documents into structured implementation plans and tasks.

Official
Advanced
jankneumannjankneumann
4

plan-roadmap

Decompose markdown proposals into prioritized OpenSpec change candidates with a dependency DAG.

Community
Advanced
EzekTec-IncEzekTec-Inc

speckit-tasks

Generate dependency-ordered implementation tasks from software feature specifications and design artifacts.

Community
Advanced