project-solution-design

Plans how a feature fits existing code and decomposes it into ordered tasks.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/envoydev/claude-stack --skill project-solution-design-envoydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-solution-design
Source: https://github.com/envoydev/claude-stack/tree/main/stack/skills/project-solution-design
Command: npx skills add https://github.com/envoydev/claude-stack --skill project-solution-design-envoydev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deciding where a new feature belongs in an existing codebase and how to break it into buildable tasks is error-prone when done ad hoc. This Skill provides a structured single-chat method to orient in the project's architecture docs, judge the architectural fit, and produce an ordered minimal task plan before any code is written. ## Core Features & Use Cases - Architecture-fit verdict: Judges whether to extend an existing seam, refactor first, or isolate a new boundary, tied to the exact dependency edge and verified against located code. - Ordered task decomposition: Produces a minimal plan where each task names its files, stack traps, file:symbol anchors, and log points, with shared files assigned a single owner so parallel builds never collide. - Decisions ledger and handoff: Records every judgment call with its precedent, writes the plan to a durable file with required Oriented and Asked headers, and hands off to plan verification, implementation, and code review skills. - Use Case: When asked to add data export to a records list, use this Skill to determine the export belongs in the existing query-projection seam, then produce a three-task plan covering the projection, the streamed entry point, and an integration test. ## Quick Start Ask the assistant to design how a new feature fits the existing codebase and break it into an ordered task plan before writing any code.

Frequently Asked Questions about project-solution-design

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

FAQPage Schema
How do I plan a feature before writing code?▼

Orient in the project's architecture docs with a scoped grep rather than a full read, judge whether the work extends an existing seam or needs a new boundary, then decompose into ordered tasks naming files, traps, anchors, and log points. Write the plan to a file before building.

How to break a code change into ordered tasks?▼

Split the work so each task owns a clear slice in dependency order, naming the files it touches and the stack traps it must handle. Give any file two tasks would both edit, like a route registry or DI composition root, exactly one owning task so parallel work never collides.

When should I not use a design planning step?▼

Skip it for a change with an obvious single home, such as a one-line edit, and just make the change. It is also not for plan audits or built-code review, which are handled by separate verification skills after the plan exists.

Can the design run in a dispatched subagent instead of the chat?▼

Yes. On an agents request, dispatch the solution-designer seat, which runs the same method in isolation and returns the plan in its report since it has no Write tool. The orchestrator then writes the plan file from that report.

Why does a plan get rejected after the build?▼

A common cause is a fit verdict judged against what the code made convenient rather than the user's actual request, such as building a side-by-side prototype when the user asked for the old path to be replaced. The Asked header line anchors the verdict to the user's verbatim words.