Projekt-Inception

Das Projekt definieren, bevor Sie eine Zeile schreiben

Führen Sie ein strukturiertes Intake-Gespräch, um Compliance-Anforderungen, Deployment-Topologie, externe Abhängigkeiten, Tech-Stack und Erfolgskriterien zu erfassen – alles in einer abgezeichneten Projektspezifikation.

Zugang anfragen

project_spec — intake output

summary: "One paragraph: what this builds and for whom"

complianceFrameworks: ["HIPAA", "SOC2 Type II"]

deploymentTargets: ["AWS ECS eu-central-1", "on-prem backup"]

externalDependencies: [{ name: "Stripe", docsUrl: "..." }]

techStack: { backend: "Fastify", frontend: "React 19" }

outOfScope: ["Mobile app (v2)", "Multi-tenancy"]

successCriteria: ["500 users in 3 months", "99.9% uptime"]

status: approved ✓

Everything Agents Need, Captured Once

Compliance First

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.

Deployment Topology

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.

External Dependencies with Docs URLs

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.

Explicit Out-of-Scope

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 Intake Conversation

The planning-inception expert follows a fixed 7-question sequence, probing for specific answers rather than accepting vague responses.

What problem does this solve? Who are the users?

Anchors the spec to real people with real needs. Vague answers are rejected — the expert probes until roles and pain points are specific.

What compliance frameworks apply?

HIPAA, SOC2, GDPR, PCI-DSS, ISO 27001, or none. Asked second because the answer changes everything downstream.

Where will this be deployed?

Cloud provider, region, on-prem, or hybrid. Data residency requirements are captured explicitly.

What external APIs or services will this integrate with?

Name, purpose, and docs URL for every integration. These become knowledge sources for future agents.

What tech stack choices have been made or are preferred?

Language, framework, database, cache, queue, auth provider, observability. Captured now to avoid conflicting choices later.

What is explicitly out of scope for v1?

At least 3 items required. Every feature mentioned implicitly expands scope — writing exclusions prevents it.

What does success look like — measurable outcomes in 3/6/12 months?

Vague success criteria ("users will be happy") are rejected. Specific, measurable outcomes only.

Spec Lifecycle

Draft

Inception in progress

→

In Review

Awaiting sign-off

→

Approved

Drives all future work

Creating a new spec for a project automatically supersedes the previous approved spec. Version history is preserved.

Jedes Projekt richtig starten

Verlieren Sie nie wieder den Überblick. Die Projektspezifikation wird zur maßgeblichen Quelle für jeden Agenten und jeden Job.

Frühzugang anfragen