skills.rest
simonwjackson
simonwjacksonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

se-plan

Create structured software plans with YAML frontmatter and unit IDs.

Updated May 7, 2026
Search Tags:#planning#documentation#requirements#subagents#software-engineering#plan-writing
One-click install
npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: se-plan
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-plan
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning complex software work is challenging; se-plan translates vague prompts into structured, durable plans, including implementation units and phase-driven guidance, while enabling interactive deepening with sub-agent findings.

Core Features & Use Cases

  • Plan creation from user prompts, requirements documents, or brainstorm outputs.
  • Deepening existing plans with sub-agent findings to refine scope and decisions.
  • Enforce plan structure with per-unit U-IDs and YAML frontmatter for consistency.
  • Support plan handoff, documentation review, and cross-team collaboration.

Quick Start

Provide a task prompt like 'plan this feature' or 'deepen my plan' and receive a complete, structured plan ready for review.

Frequently Asked Questions about se-plan

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

FAQPage Schema
How do I create structured software development plans from vague requirements?▼

Software planning tools structure vague prompts into durable blueprints using per-unit U-IDs and YAML frontmatter. They organize multi-step tasks into phases, ensuring execution-ready documentation for development handoff.

What is the best way to deepen existing software plans with sub-agent findings?▼

Deepening software plans applies sub-agent findings to refine scope and decisions interactively. This updates the existing blueprint, ensuring the structured plan accurately reflects new technical discoveries and remains execution-ready.

How do I write software requirements documentation that is ready for execution?▼

Execution-ready requirements documentation applies YAML frontmatter, per-unit U-IDs, and phase-aware organization to software tasks. This structure defines clear interfaces for resourcing, tests, and team handoff.

Can I use brainstorm outputs to generate multi-step software task blueprints?▼

Yes, software planning accepts brainstorm outputs as input to generate multi-step task blueprints. It structures these outputs into durable plans complete with implementation units and phase-aware organization for execution.

How do you organize multi-step software tasks for cross-team collaboration?▼

Organizing multi-step software tasks for cross-team collaboration requires phase-aware organization and per-unit U-IDs within a durable blueprint. This structure supports plan handoff, documentation review, and clear interfaces for resourcing and tests.

Related Skills

Explore More Software Engineering Skills→
DIO0550DIO0550
1

system-design

Generate system design documents, ADRs, and C4 diagrams in Markdown.

Community
Advanced
softbreezeesoftbreezee

writing-plans

Draft step-by-step implementation plans with tasks, files, tests, and milestones.

Community
Advanced
All-The-VibesAll-The-Vibes
50

deepen-plan

Coordinate parallel research agents to deepen plan sections with best practices.

Official
Advanced
danicolmsdanicolms
1

AI-Human Attribution Tracking Skill

Track human and AI contributions across software development phases.

Community
Advanced