PromptEngineering

A Specification Pipeline built from ready-to-use engineering patterns.

Spec-driven · Staff patterns

6 Steps

The anatomy of a good SPEC.

A SPEC resembles a PRD (Product Requirements Document) — the classic artifact of Product Management. The difference: a PRD defines what the product must do for the business; the SPEC adapts that rigor to the engineering cycle, ensuring alignment before any line of code is written.

1

THE WHY

1. Context

A Spec is not a task list — it's a business argument. Define the problem and why solving it matters now.

2

THE IMPACT

2. Success Metrics

If there's no measurable success criterion, the Spec is empty. Define what winning looks like.

3

THE WHAT

3. Scope & Scenarios

User stories grounded in Jobs-to-be-Done. Cover the real journey — from the happy path to the failure case.

4

THE RULES

4. Constraints & Rules

Business rules and technical guardrails. The tracks where any valid solution must run.

5

THE BOUNDARIES

5. Out of Scope

Defining what will NOT be built is as important as defining what will. First defense against scope creep.

6

THE CHECKPOINT

6. Definition of Done

A non-negotiable contract. Done is only true when it's technically correct, functionally tested, and visually complete.

In Practice

A complete specification, filled start to finish.

Prompt Builder

Pick a track and generate your first specification.

Prompt Builder

Step 1/2: Select Project Type

Select Project Type

PistasPick the project type. Each track generates a SPEC template for your agent.

PromptEngineering

6 Steps

1. Context

2. Success Metrics

3. Scope & Scenarios

4. Constraints & Rules

5. Out of Scope

6. Definition of Done

In Practice

Prompt Builder

Prompt Builder

Select Project Type

Lite mode

New evolution

Legacy modernization