aibdd-specformula

Translate a new requirement into plan.md and eight Phase cards.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-specformula
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aibdd-specformula
Source: https://github.com/zenbuapps/zenbu-powers/tree/main/skills/aibdd-specformula
Command: npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-specformula

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill translates a new requirement into a complete, structured engineering plan, generating plan.md and eight Phase cards to guide cross-functional delivery.

Core Features & Use Cases

  • Generate an Execution Plan and 8 Phase cards from a single requirement.
  • Delegate execution to /aibdd-carry-on-engineering-plan for human-in-the-loop review and iterative execution.
  • Trigger on keywords like specformula or 新需求 to start the full development lifecycle.

Quick Start

Describe a new requirement and ensure arguments.yml exists to trigger the full planning workflow.

Frequently Asked Questions about aibdd-specformula

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

FAQPage Schema
How do I generate a full engineering execution plan from a new requirement?

To generate an engineering execution plan, describe a new requirement to trigger the workflow, which outputs a structured plan.md and eight Phase cards to guide cross-functional project delivery.

How does BDD phase management work for cross-functional projects?

BDD phase management works by translating requirements analysis into eight phase cards, enforcing prerequisites and lazy loading to structure iterative execution and review across cross-functional teams.

Do I need any specific configuration to start requirements analysis for execution planning?

Yes, you need an arguments.yml file to exist in your environment to trigger the full planning workflow and enforce prerequisites before generating any execution plan artifacts.

What is the best way to handle iterative review after generating an execution plan?

The best way to handle iterative review is delegating the generated execution plan to a carry-on engine, enabling human-in-the-loop review and iterative execution for subsequent phases.

Are there limitations when using lazy loading for phase management?

Lazy loading limitations require strict enforcement of prerequisites before execution, meaning phase cards and plan.md artifacts must be fully generated and resolved before downstream iterative review can proceed.

Can I use pyyaml to configure automation for requirements analysis?

Yes, you can use pyyaml to configure automation by defining arguments.yml, which provides the necessary input data formats to trigger the full requirements analysis and planning workflow.