solo-dev-design

Produces four confirmed development design documents covering logic, data models, data access, and API contracts before coding.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-dev-design-cjrain-12505614
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solo-dev-design
Source: https://github.com/cjrain-12505614/solo-forge-marketplace/tree/main/solo-forge-v1.2.0/skills/solo-dev-design
Command: npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-dev-design-cjrain-12505614

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When feature specs and screen designs exist but coding starts immediately, implementation fills in data structures, API shapes, and flows with on-the-fly guesses. This Skill finalizes confirmed design values right before coding, bridging the gap between feature planning and implementation. ## Core Features & Use Cases - Four-part design set: Produces one document with four sections in dependency order — logic/workflow (hub), data model (entities, constraints, migrations), data access (queries/ORM with N+1 risk flags), and API contracts (endpoints, schemas, error codes). - Traceability keys: Attaches tracking keys (REQ/AC, SCR, LOGIC/TBL/API-NN) so requirements, screens, design, and implementation can be cross-verified via grep. - Independent verification gate: Drafts are cross-checked with a consistency-check pass and an approval gate before implementation begins; unconfirmed items stay marked as needing confirmation. - Use Case: Before building a new order-management feature, generate the confirmed design set so the coding agent implements against fixed table schemas and API contracts instead of guessing. ## Quick Start Ask the AI to create the development design for a feature, finalizing the logic flow, data model, data access patterns, and API contracts before any coding starts.

Frequently Asked Questions about solo-dev-design

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

FAQPage Schema
How do I create a development design document before coding?▼

Write one design document with four sections in dependency order: logic/workflow as the hub, then data model, data access, and API contracts. Confirm each value before implementation and mark anything undecided as needing confirmation.

What should an API contract specification include?▼

An API contract should define endpoints with method and path, request parameters and body schemas, success response schemas with status codes, error responses with codes and meanings, and authentication requirements, detailed enough for a client to integrate directly.

Does this design approach work with any tech stack?▼

Yes, the design method is stack-agnostic. It detects the project's stack from build markers and existing code, then expresses data access and models using that stack's conventions rather than fixed ORM or query syntax.

How do I trace requirements to design and implementation?▼

Attach tracking keys to each design item, such as REQ/AC for requirements, SCR for screens, and LOGIC/TBL/API-NN for design elements. This lets you join and cross-verify requirements, design, and code with grep.

When can I skip writing a full development design?▼

Small features can skip it since the process is non-mandatory. The value is largest for features where data models and APIs are intertwined and guessing during implementation would be costly.