From beta-planning
Gathers context, writes Verification and Solution tabs for a beta task. Use when 'beta solution', 'beta new solution', 'beta verification', or after beta requirements are approved. Not for markdown solutions (use new-solution instead).
How this skill is triggered — by the user, by Claude, or both
Slash command
/beta-planning:beta-new-solutionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Read approved requirements, gather codebase context, write `context.md`, then add Verification and Solution tabs to `plan.html`.
Read approved requirements, gather codebase context, write context.md, then add Verification and Solution tabs to plan.html.
Part of the beta planning workflow. See references/beta-workflow-overview.md for the full pipeline.
Find task folder -- identify the active task from recent context, user input, or by scanning docs/tasks/ for the latest folder. Read plan.html and check the Requirements tab. Verify all Open Questions are resolved -- if not, resolve them first.
Scan skills -- check available skills for topic matches relevant to this task's domain. Load matched skills.
Gather codebase context -- spawn 2 parallel subagents to ground the design in codebase reality:
CB1 (Code):
CB2 (Docs):
autosearch quickstart to discover available search tools, then use the best fit if usefulCollect findings from both subagents before proceeding.
Write context.md -- combine the findings into context.md in the task folder.
See references/template-context.md for the template and rules.
Scan for verification strategies -- check available project skills for testing, verification, and assurance strategies. Load any matched skills.
Write Verification tab -- using the context and requirements, design the verification strategy. Insert <pd-tab name="Verification"> into plan.html after the Requirements tab.
See references/tab-verification.md for the tab structure and rules.
Hard-stop (gate 1) -- present the Verification tab to the user. Tell them: "Review the Verification tab. When ready, confirm to proceed to Solution design."
Assess complexity (informed by context):
Explore options -- spawn parallel subagents, one per candidate approach. Each subagent investigates feasibility using the gathered context. Collect results. Present a comparison table with pros/cons for each option. Wait for the user to pick.
Write Solution tab -- design the solution and insert <pd-tab name="Solution"> into plan.html after the Verification tab.
See references/tab-solution.md for the tab structure and rules.
Validate assumptions -- review every design decision and identify any that were NOT clearly dictated by (a) the requirements or (b) pre-established patterns in the repository. Surface uncertain decisions with the user (use AskUserQuestion tool). Update plan.html with their answers.
Hard-stop (gate 2) -- present the completed Solution tab to the user. Do NOT proceed to the plan stage. Tell them: "Review the Solution tab. When ready, run /beta-new-plan to continue."
npx claudepluginhub mistakenot/skills --plugin beta-planningProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.