planning-skill

Convert approved specs into delivery plans with workstreams and validation gates.

7|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/MajesteitBart/delano --skill planning-skill-majesteitbart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-skill
Source: https://github.com/MajesteitBart/delano/tree/main/.agents/skills/planning-skill
Command: npx skills add https://github.com/MajesteitBart/delano --skill planning-skill-majesteitbart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns an approved specification into a concrete delivery plan with clear workstream boundaries, so teams can move from intent to execution without improvising the structure.

Core Features & Use Cases

  • Plan Drafting: Produces a plan.md aligned to the approved spec and architecture constraints.
  • Workstream Decomposition: Breaks the plan into owned workstream files with explicit dependencies and handoff criteria.
  • Validation and Recovery: Checks architectural decisions, rollout, rollback, and conflict risks before execution proceeds.
  • Use Case: A product or engineering lead can feed in a reviewed spec and get a structured plan that is ready for implementation tracking.

Quick Start

Ask the planning skill to convert an approved spec into a delivery plan and initial workstreams.

Frequently Asked Questions about planning-skill

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

FAQPage Schema
How do I turn an approved specification into an executable delivery plan?

To turn an approved specification into an executable delivery plan, provide the spec as input to generate a structured plan.md with defined workstream boundaries, validation gates, and documented rollout paths.

What is workstream decomposition in software delivery planning?

Workstream decomposition breaks a delivery plan into owned workstream files with explicit dependencies and handoff criteria, allowing teams to move from intent to execution without improvising the structure.

How do I validate architecture decisions and rollback paths before execution?

Validating architecture decisions and rollback paths requires checking documented rollout procedures and conflict risks against the approved spec before execution proceeds to ensure safe delivery.

What do I need to generate a structured plan for implementation tracking?

Generating a structured plan for implementation tracking requires explicit spec inputs, justified architecture decisions, and documented rollout paths to produce aligned workstream files.

Does delivery planning work without an explicit spec approval?

Delivery planning requires explicit spec inputs and justified architecture decisions, so proceeding without an approved specification prevents generating a valid plan with validation gates.

Can I use this for post-approval architecture coordination across shared filesystems?

Yes, applying post-approval planning for software delivery supports architecture coordination and task decomposition across shared filesystems to generate executable workstreams.