plan-b
Plan B
Overview
Produce a strong, concise plan by combining multiple plan variants from subagents, then synthesize a single best plan with an ASCII diagram.
Workflow (follow in order)
-
Scan context quickly (read-only)
- Read
README.mdand obvious docs (docs/,CONTRIBUTING.md,ARCHITECTURE.md). - Skim relevant files (likely touchpoints).
- Identify constraints (language, frameworks, CI/test commands, deployment shape).
- Read
-
Ask follow-ups only if blocking
- Ask at most 1-2 questions.
- Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
- If unsure but not blocked, make a reasonable assumption and proceed.
-
Spawn subagents for plan variants
More from bohdan-shulha/skills
qt-qml-attachments
>-
17commit-jira
Create and execute Git commits with a required JIRA-style subject and required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit and expects a ticket-prefixed subject. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.
10claude-cli-agent-protocol
>-
10commit
Create and execute Git commits in Conventional Commits format with a required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.
9repo-wiki
Generate and maintain a living repo wiki, specs, PRDs, and architecture docs in .repo-wiki/ so coding agents can navigate the codebase with strong context. Use for codebase discovery, PR-driven documentation updates, module docs, architecture maps, feature specs, and deleting stale knowledge when code changes.
1