Run any Skill in Manus with one click

bmad-autonomous-planning

Stars5

Forks0

UpdatedMarch 29, 2026 at 20:23

Portable autonomous BMALPH planning for Codex. Use when the user wants specs from a short task description and expects the current AI session to orchestrate BMALPH subagents without human interaction.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

VilnaCRM-Org

VilnaCRM-Org/core-service

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	bmad-autonomous-planning
description	Portable autonomous BMALPH planning for Codex. Use when the user wants specs from a short task description and expects the current AI session to orchestrate BMALPH subagents without human interaction.

Use this skill from the current Codex session. Do not rely on repo-local bash wrappers, make targets, or other launcher automation for the planning flow.

The canonical planning contract lives in .claude/skills/bmad-autonomous-planning/SKILL.md. This wrapper is only the Codex-specific handoff.

If _bmad/ is missing, stop and tell the user BMALPH assets must be initialized for the repository before this skill can run. Otherwise:

Read the local bmalph skill wrapper, _bmad/COMMANDS.md, and the resolved BMAD config file first.
Read .claude/skills/bmad-autonomous-planning/SKILL.md.
Resolve or create a bundle directory under the configured planning artifacts folder, typically autonomous/<timestamp>-<task-slug>/.
Run each BMALPH planning stage in a dedicated subagent, using the BMALPH command surface as the handoff contract:
- research and repository context: analyst
- product brief: create-brief
- PRD: create-prd
- architecture: create-architecture
- epics and stories: create-epics-stories
- implementation readiness: implementation-readiness
After each subagent returns, the main agent must decide the next step, answer workflow questions on the user's behalf, and only then hand the next stage to another subagent.
Validate and improve each artifact for up to three rounds without blocking on BMALPH approval menus. When another subagent pass is needed, prefer the matching BMALPH validation command from _bmad/COMMANDS.md when available.
For every spawned planning or validation subagent, set model: gpt-5.4 and reasoning_effort: xhigh. Do not use gpt-5.4-mini for stage ownership in this workflow.

For each subagent, name the BMALPH command first and provide only the backing workflow or agent files required by that command. Do not hand off raw workflow-file paths without the command context.

Minimal Codex trigger example:

Use the bmad-autonomous-planning skill to plan customer tagging for the core service. Follow the repository's BMALPH autonomous planning skill, work in the current session, keep the flow fully autonomous, and run each planning subagent on gpt-5.4 with xhigh reasoning.

The finished bundle should include:

research.md
product-brief.md
product-brief-distillate.md when useful
prd.md
architecture.md
epics.md
implementation-readiness.md
run-summary.md

Optional GitHub issue or specs-only PR work happens only after the planning bundle is complete and only when the user explicitly asks for it.

More from this repository

same repository

ci-workflow

VilnaCRM-Org/core-service

Run comprehensive CI checks before committing changes. Use when the user asks to run CI, run quality checks, validate code quality, or before finishing any task that involves code changes.

2026-05-175

code-organization

VilnaCRM-Org/core-service

Ensure proper code organization with class names, directories, namespaces, and naming consistency following the principle "Directory X contains ONLY class type X".

2026-05-175

implementing-ddd-architecture

VilnaCRM-Org/core-service

Design and implement DDD patterns (entities, value objects, aggregates, CQRS). Use when creating new domain objects, implementing bounded contexts, designing repository interfaces, or learning proper layer separation. For fixing existing Deptrac violations, use the deptrac-fixer skill instead.

2026-05-175

cache-management

VilnaCRM-Org/core-service

Implement production-grade caching with cache keys/TTLs/consistency classes per query, SWR (stale-while-revalidate), layered explicit invalidation, and comprehensive testing for stale reads and cache warmup. Use when adding caching to queries, implementing cache invalidation, or ensuring cache consistency and performance.

2026-04-265

code-review

VilnaCRM-Org/core-service

Systematically retrieve and address PR code review comments using make pr-comments. Enforces DDD architecture, code organization principles, and quality standards. Use when handling code review feedback, refactoring based on reviewer suggestions, or addressing PR comments.

2026-04-055

developing-openapi-specs

VilnaCRM-Org/core-service

Guide for contributing to the OpenAPI layer using processor pattern, complexity management, and functional programming. Use when adding endpoint factories, processors, parameter descriptions, reducing cyclomatic complexity, or fixing OpenAPI validation errors. Covers architecture patterns from user-service repository.

2026-04-055

name	bmad-autonomous-planning
description	Portable autonomous BMALPH planning for Codex. Use when the user wants specs from a short task description and expects the current AI session to orchestrate BMALPH subagents without human interaction.

Use this skill from the current Codex session. Do not rely on repo-local bash wrappers, make targets, or other launcher automation for the planning flow.

The canonical planning contract lives in .claude/skills/bmad-autonomous-planning/SKILL.md. This wrapper is only the Codex-specific handoff.

If _bmad/ is missing, stop and tell the user BMALPH assets must be initialized for the repository before this skill can run. Otherwise:

Read the local bmalph skill wrapper, _bmad/COMMANDS.md, and the resolved BMAD config file first.
Read .claude/skills/bmad-autonomous-planning/SKILL.md.
Resolve or create a bundle directory under the configured planning artifacts folder, typically autonomous/<timestamp>-<task-slug>/.
Run each BMALPH planning stage in a dedicated subagent, using the BMALPH command surface as the handoff contract:
- research and repository context: analyst
- product brief: create-brief
- PRD: create-prd
- architecture: create-architecture
- epics and stories: create-epics-stories
- implementation readiness: implementation-readiness
After each subagent returns, the main agent must decide the next step, answer workflow questions on the user's behalf, and only then hand the next stage to another subagent.
Validate and improve each artifact for up to three rounds without blocking on BMALPH approval menus. When another subagent pass is needed, prefer the matching BMALPH validation command from _bmad/COMMANDS.md when available.
For every spawned planning or validation subagent, set model: gpt-5.4 and reasoning_effort: xhigh. Do not use gpt-5.4-mini for stage ownership in this workflow.

For each subagent, name the BMALPH command first and provide only the backing workflow or agent files required by that command. Do not hand off raw workflow-file paths without the command context.

Minimal Codex trigger example:

The finished bundle should include:

research.md
product-brief.md
product-brief-distillate.md when useful
prd.md
architecture.md
epics.md
implementation-readiness.md
run-summary.md

Optional GitHub issue or specs-only PR work happens only after the planning bundle is complete and only when the user explicitly asks for it.