S01Specification workflow

Define behavior first. Preserve the path to delivery.

This example documents a proposed CSV task-import feature as a specification, technical plan, and dependency-ordered task list.

Product behavior / technical decisions / verifiable work

The generated documents describe the proposed feature; they do not implement it. Stable identifiers connect requirements and acceptance criteria to design choices, tasks, and named tests without collapsing those concerns into one document.

S02Source-defined task

The method names below are plain-language instructions, not a fixed builder API. The dynamic task records them in order and sends the resulting statement to the selected coding agent.

Program.cs / excerpt

Builder.WithFile("AGENTS.md", options)
    .CreateOrReplaceAgentInstructionsForSpecificationDrivenDevelopment("AGENTS.md")
    .BaseTheWorkflowOnConsumerVisibleBehaviorBeforeImplementationDetails()
    .RequireExplicitScopeNonGoalsAssumptionsEdgeCasesAcceptanceCriteriaAndOpenQuestions()
    .RequireTraceabilityFromRequirementsToPlanToVerificationTasks()
    .CreateOrReplaceProjectConstitution(".specify/memory/constitution.md")
    .CreateOrReplaceSpecificationIndex("specifications/README.md")
    .WriteProductSpecification("specifications/csv-task-import/spec.md", productBrief)
    .WriteTechnicalPlan("specifications/csv-task-import/plan.md", planningBrief)
    .WriteDependencyOrderedTasks("specifications/csv-task-import/tasks.md", taskBrief)
    .CiteTheResearchSourcesAlreadyNamedInTheProgramWithoutCopyingTheirText()
    .DoNotModifyProgramProjectFilesOrBuilderSource()
    .ValidateMarkdownLinksAndCrossArtifactTraceability()
    .WithConciseOutput();

The actual source includes the complete product, planning, and task briefs. Read Program.cs to see the full statement and its execution options.

S03Run safely

Run from the complete repository checkout. The project file links ../../SuperIntelligenceBuilder.cs, so this directory is not a standalone download.

cd examples/specification-workflow
dotnet build
dotnet run

The default command is a dry run. See the shared example steps for preview and live-run prerequisites.

live execution

dotnet run -- --yes,please,proceed

This checkout already contains AGENTS.md. The live command therefore requires the exact reply yes, please proceed; no stops. Review the resulting specification diff. The complete state table and consent scope are under Execution and completion.

S04Inspect the outputs

Output	Reader purpose
`AGENTS.md`	Instructions an agent must follow when maintaining this example.
`constitution.md`	Durable principles and gates for specification-driven work.
`specifications/README.md`	An index and reading order for the specification set.
`spec.md`	User-visible behavior, scope, requirements, acceptance criteria, and open questions.
`plan.md`	Technical boundaries, decisions, verification, rollout, and rollback.
`tasks.md`	Dependency-ordered work mapped to acceptance criteria and tests.

S05Basis and evidence

The source asks for GitHub Spec Kit’s separation of constitution, specification, plan, and tasks, and for the product-behavior emphasis represented by Warp’s write-product-spec skill. These are stated influences, not copied templates or a claim that one skill is objectively best.

The checked-in result came from an authenticated builder-driven Codex run. Local checks found 12 valid Markdown links, 17 requirements, 15 acceptance criteria, 8 plan decisions, 11 named tests, and 12 dependency-ordered tasks with no reported traceability errors. See the validation record for the commands and limits of that evidence.