Minimal Plan
This example shows the smallest useful APS plan.
Single-file plan
For small projects, one file is enough:
# Todo App
A simple todo list application.
## Problem
Users need to track tasks.
## Success Criteria
- [ ] Users can add todos
- [ ] Users can list todos
## Work Items
### TODO-001: Initial setup
- **Intent:** Project structure created with working build
- **Expected Outcome:** `npm run build` exits 0
- **Validation:** `npm run build`
### TODO-002: Add todo endpoint
- **Intent:** POST /todos creates a new todo item
- **Expected Outcome:** Endpoint returns 201 with created todo
- **Validation:** `npm test -- todos.create.test.ts`
### TODO-003: List todos endpoint
- **Intent:** GET /todos returns all todos for user
- **Expected Outcome:** Endpoint returns paginated list filtered by user
- **Validation:** `npm test -- todos.list.test.ts`
Why this works
Even this minimal plan provides:
Clear outcomes
Each work item has a single, measurable outcome. You know when it is done.
Validation commands
Tests prove completion. No ambiguity.
Observable checkpoints
When you need more granularity, add an action plan — but simple items do not require one.
When to grow
Upgrade to multi-file when:
- More than 5–7 work items
- Multiple distinct features or modules
- Multiple people working concurrently
Template
Copy this template for new projects:
# {Project Name}
## Problem
{Brief problem statement}
## Success Criteria
- [ ] {Observable outcome}
## Work Items
### {PREFIX}-001: {Title}
- **Intent:** {What success looks like}
- **Expected Outcome:** {Testable result}
- **Validation:** `{command}`
Next: Multi-module example →