Define the Project Before You Write a Line
Run a structured intake conversation to capture compliance requirements, deployment topology, external dependencies, tech stack, and success criteria — all in one signed-off project spec.
Run a structured intake conversation to capture compliance requirements, deployment topology, external dependencies, tech stack, and success criteria — all in one signed-off project spec.
Ask about HIPAA, SOC2, GDPR, and PCI-DSS upfront — not after the schema is set. Compliance requirements shape database design, logging, and infrastructure from day one.
Cloud vs. on-prem vs. hybrid is not a detail — it's a constraint. The spec locks in where data lives, which regions apply, and what the network boundary looks like.
Every integration is listed with a documentation URL. That URL becomes a knowledge source. Agents never work with stale API knowledge — they pull from the versioned docs you specified.
Every unwritten assumption becomes a scope creep vector. The spec demands at least 3 out-of-scope items — not because the list is complete, but because writing it forces discipline.
The planning-inception expert follows a fixed 7-question sequence, probing for specific answers rather than accepting vague responses.
Anchors the spec to real people with real needs. Vague answers are rejected — the expert probes until roles and pain points are specific.
HIPAA, SOC2, GDPR, PCI-DSS, ISO 27001, or none. Asked second because the answer changes everything downstream.
Cloud provider, region, on-prem, or hybrid. Data residency requirements are captured explicitly.
Name, purpose, and docs URL for every integration. These become knowledge sources for future agents.
Language, framework, database, cache, queue, auth provider, observability. Captured now to avoid conflicting choices later.
At least 3 items required. Every feature mentioned implicitly expands scope — writing exclusions prevents it.
Vague success criteria ("users will be happy") are rejected. Specific, measurable outcomes only.
Creating a new spec for a project automatically supersedes the previous approved spec. Version history is preserved.
Never lose context again. The project spec becomes the authoritative source for every agent, every job, for the life of the project.
Request Early Access