FOR AGENCIES
Start client work with a written project baseline
Share a structured kit covering requirements, decisions, architecture, and delivery tasks. When the project changes, review the proposed impact and price before accepting an update.
Answer intelligent project questions and generate a complete PRD, architecture, implementation plan, coding-agent instructions, custom skills, and specialist agents.
The same idea, handed to the same agent, with and without a build kit.
Four steps, one session.
A few sentences of plain language is enough to start.
Questions branch on your answers and stop when coverage is solid.
Accept, reject or modify each section before it lands in the kit.
One folder your coding agent reads before it writes a line.
Twelve artifact types, each cross-referenced by requirement ID.
Scope, users, constraints, non-goals.
Components, boundaries, decision records.
Step-by-step paths with states and edge cases.
Entities, relations, migrations, retention.
Endpoints, payloads, errors, auth rules.
Phased sequence with dependencies.
Agent-sized units, each citing a requirement.
Given / when / then per requirement.
Unit, integration and manual coverage map.
Specialists scoped to your stack and domain.
Reusable procedures the agent can invoke.
The entry file your agent reads first.
Instruction files are emitted in each agent's expected format. The kit itself is plain markdown.
Keep an accepted project version as its baseline, then review proposed changes before deciding how to proceed.
Explore the sample kitCreate a project baseline from your interview.
Review and accept the generated project version.
Describe what has changed in your project.
See the affected project context, scope, and price before approval.
Choose a priced update or re-baseline when offered.
FOR AGENCIES
Share a structured kit covering requirements, decisions, architecture, and delivery tasks. When the project changes, review the proposed impact and price before accepting an update.
FOR FREELANCE DEVELOPERS
Bring requirements, plans, and coding-agent instructions together in a downloadable kit, then use it with a supported coding agent or plain Markdown workflow.
Per project. No subscription.
Review the proposed scope and price before approving a change.
Describe the change to see its estimated impact on the accepted project context. Before you approve, the proposed change type and price are shown. Choose whether to continue with the offered update or re-baseline.
Before accepting a version, you can request a free correction for something Scafino misunderstood or generated incorrectly. After acceptance, new project changes use the priced update flow.
The kit includes instruction formats for Claude Code, Codex, Cursor, Windsurf, and GitHub Copilot, plus plain Markdown for other workflows. See the sample kit.
A downloadable Build Kit with project requirements, architecture, plans, acceptance criteria, tests, and coding-agent context. Browse the sample kit to see its files.
Give it a system to build from.