On this pageOpenClose
Phase 01
Discovery
Shapes the work. I hold the wheel; the agent helps me think.
Operating model
Developer zone
- Feature spec
- Define intent + context
- Focused task approved
Agent zone
- Thinking agent
- Questions
- Risks
- Draft splits
No coding.
No approval authority.
Feedback runs between the two zones.
I hold the wheel during Discovery.
The agent helps me think, challenge, and split work.
I approve the focused task before Implementation starts.
1.1 Definitions
Spec
- The spec is the main ClickUp ticket.
- It describes the full feature slice.
- It contains the formal acceptance criteria.
Acceptance criterion
- An acceptance criterion becomes a ClickUp sub-task ticket.
- The sub-task is the focused task.
- The focused task is what gets handed to Implementation.
Focused task
- A focused task is one agent-sized unit of work.
- It must fit one reviewable PR.
- If it cannot fit, it gets split before coding.
1.2 Discovery tree
Intent Engineering Pain Impact Scope Specification Context Engineering Domain map Data map Execution map Map gaps Implementation Plan Criteria-to-PR order Sequencing Risks Quality gates Evaluation PR boundary Context Carry Forward Discovery Exit Gate
1.3 Discovery gate
- What should be true?
- What should not be changed?
- What proof will show it works?
- What context does the agent need?
- Can this stay under 100 LOC including docs?
1.4 Discovery rules
- Start with the workflow.
- Add abstractions only when the pattern repeats.
- Keep business rules server-side.
- Keep UI as input, output, and state display.
- Do not use production as the test environment.
- Preserve context for the next agent and the next reviewer.