dev-plan

Generate development plans from validated DSLs and scenarios.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/unicorn-plugins/abra --skill dev-plan-unicorn-plugins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-plan
Source: https://github.com/unicorn-plugins/abra/tree/main/skills/dev-plan
Command: npx skills add https://github.com/unicorn-plugins/abra --skill dev-plan-unicorn-plugins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev-plan automates the creation of a comprehensive development plan from validated DSLs and scenarios, saving teams time and ensuring consistency across architecture, technology stacks, and testing strategies.

Core Features & Use Cases

  • Phase 1: non-functional requirements collection to guide planning.
  • Phase 2: generation of a complete development plan using a planner/architect workflow.
  • Phase 3: formal review to verify consistency and completeness of the plan.

Quick Start

Trigger the dev-plan phase with /abra:dev-plan once a valid DSL and scenario exist.

Frequently Asked Questions about dev-plan

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

FAQPage Schema
How do I automate end-to-end development planning from validated scenarios?

Automate end-to-end development planning by using a planner and architect workflow to generate a comprehensive plan from validated DSLs and scenarios. This process ensures consistent architecture, tooling, and deployment strategies across software projects.

What is a DSL validation and review orchestration process in software planning?

DSL validation and review orchestration is a structured process that verifies input domain-specific languages before generating a development plan, then formally reviews the output to ensure consistency, completeness, and correct technology stack alignment.

How do I generate a comprehensive development plan for consistent architecture and testing strategies?

Generate a comprehensive development plan by triggering an automated planner execution after non-functional requirements collection. This workflow produces consistent architecture, technology stacks, and testing strategies for software teams.

Do I need a valid DSL and scenario before I start automated development planning?

Yes, a valid DSL and scenario must exist before you trigger the development planning workflow. The process enforces a structured phase sequence starting with non-functional requirements collection and DSL validation before generating the plan.

What's the best way to structure a formal review for a software development plan?

The best way to structure a formal development plan review is through an orchestrated review phase that verifies the completeness and consistency of the generated architecture and deployment strategies against the initial scenarios.