One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-plan-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-plan
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/dev-plan
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill dev-plan-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev-plan prevents rework and scope creep by transforming broad, unclear requests into a structured, user-aligned engineering plan with explicitly gathered requirements.

Core Features & Use Cases

  • Optional interview workflow: Automatically switches to interactive requirements gathering when the request is broad or vague.
  • Direct planning for detailed requests: Skips interviews and produces a plan immediately when requirements are already specific.
  • Review mode for existing plans: Critically evaluates an existing plan to improve quality and testability.
  • Quality-gated output: Enforces that codebase claims are supported (file:line) and that acceptance criteria are testable, listing open questions and trade-offs.
  • Handoff-ready execution: Produces a plan that can be passed to @bolt-executor (implementation) or used to chain into dev-autopilot for end-to-end execution.

Quick Start

Ask the AI to dev-plan your feature by saying: "Dev-plan a workstream to implement an API client for my service, including requirements I may have missed and testable acceptance criteria."

Frequently Asked Questions about dev-plan

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

FAQPage Schema
How do I turn vague software ideas into a structured engineering plan?

To turn vague ideas into an engineering plan, you need a requirements gathering process that clarifies scope through interactive interviews. This approach converts broad requests into structured, user-aligned plans with testable acceptance criteria before any coding begins.

What is the best way to gather codebase facts for feature implementation planning?

Gathering codebase facts for feature implementation requires analyzing existing code to support structural claims with exact file and line references. This ensures your engineering plan is grounded in actual architecture rather than assumptions, preventing rework and scope creep.

Can I skip the requirements interview if my feature request already has detailed specifications?

Yes, you can skip the requirements interview if your feature request is already specific. The planning workflow features a direct mode that bypasses interactive questioning and immediately generates a quality-gated engineering plan based on your detailed specifications.

How do I review an existing engineering plan to improve its quality and testability?

Reviewing an existing engineering plan to improve testability involves critically evaluating it against quality gates. This review mode checks that codebase claims are supported by file and line references, verifies acceptance criteria are testable, and highlights open questions and trade-offs.

How do I hand off an engineering plan to an agent for end-to-end execution?

To hand off an engineering plan to an agent for execution, you produce a handoff-ready plan document that can be passed directly to implementation agents. This enables chaining into end-to-end execution workflows for actual feature implementation.