Skip to content

Full project

This profile does not build features. It makes the foundation and the backlog. Each feature then runs as an app-slice.

Use when

  • A repo is new, or a large new area starts.

Do not use when

  • The work fits in one feature. Use app-slice.

Flow

  1. Run the shaper with the human. Write the project foundation: mission, non-goals, principles, tech stack, roadmap, and the personas file (constitution/personas.md).
  2. A human approves the foundation (G1).
  3. Start the planner in a fresh session. It writes:
  4. The architecture rules as fitness checks (K8), not as prose.
  5. The walking skeleton: the smallest app that builds, deploys, and runs one end-to-end test.
  6. A backlog of app slices, in order. Each slice has acceptance criteria, a test oracle, and the personas that it serves.
  7. A human approves the architecture and the backlog (G2).
  8. Build the walking skeleton as the first app slice. Its checks become the baseline for all later slices.
  9. Run the generator for the repo. It writes the instruction file, roles, hooks, and CI checks.
  10. A human approves the setup PR (G4).
  11. Start each later slice with the app-slice profile.

Exit criteria

  • The walking skeleton passes all baseline checks in CI.
  • The backlog has at least the first 3 slices with complete Definition of Ready fields.
  • The instruction file is under the line limit (K15).
  • The personas file passes K18. Each persona has 3 to 5 job stories.

Failure handling

Failure Action
A principle cannot be a check Keep it as an instruction. Fill why_not_a_check in the manifest.
The first slices are vague Stop. The first tickets set the pattern for all others. Shape them again.

Evidence

Dossier IDs: C3, C7, D10, D11, D12, D13, A7, A10, H2.