new-solution

Generates context, verification, and solution design tabs for approved task requirements.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill new-solution-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-solution
Source: https://github.com/mistakenot/skills/tree/main/plugins/planning-workflow/skills/new-solution
Command: npx skills add https://github.com/mistakenot/skills --skill new-solution-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning approved requirements into a concrete, codebase-grounded solution design is slow and error-prone when done ad hoc. This Skill automates the design stage of a planning workflow: it gathers codebase context, defines how the work will be verified, and writes a solution design into the task's plan.html document. ## Core Features & Use Cases - Parallel Context Gathering: Spawns two subagents (code and docs) to ground the design in real codebase patterns, then writes a context.md file. - Verification Tab Generation: Designs a test strategy with Given/When/Then acceptance criteria inserted as a Verification tab in plan.html. - Solution Tab with Tradeoffs: Explores multiple approaches via parallel subagents when the task is ambiguous, records rejected alternatives, and writes the chosen design as a Solution tab. - Interactive and Autonomous Modes: Asks the user to resolve open questions when interactive, or records decisions as gated pd-question elements with recommended answers when running unattended. - Use Case: After requirements for a new API endpoint are approved, run this Skill to produce context.md plus Verification and Solution tabs in plan.html, ready for review before the planning stage. ## Quick Start Ask the agent to write a solution for the current task, for example: "Design the solution for the approved requirements in the latest task folder."

Frequently Asked Questions about new-solution

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

FAQPage Schema
How do I generate a solution design from approved requirements?▼

Run the new-solution skill after requirements are approved. It gathers codebase context with parallel subagents, writes context.md, then adds Verification and Solution tabs to plan.html in the task folder.

How does the skill handle multiple possible implementation approaches?▼

When a task is ambiguous, it spawns one subagent per candidate approach to investigate feasibility. Interactively it presents a pros/cons comparison for the user to pick; autonomously it selects the evidence-backed option and records the rest under Rejected Alternatives.

Can new-solution run autonomously without user interaction?▼

Yes. When told not to ask or no user is available, it proceeds on recommended answers recorded as gated pd-question elements in plan.html, so a human can later approve each decision in one click.

What artifacts does the solution design stage produce?▼

It produces context.md in the task folder plus two new tabs in plan.html: a Verification tab with test strategy and acceptance criteria, and a Solution tab describing the approach, file changes, and rejected alternatives.

When should I not use new-solution?▼

Do not use it before requirements exist or while open questions remain unresolved in interactive mode. It is a design stage only and hard-stops before planning; run new-plan afterward to continue the workflow.