Phase 4: Application & Habit (Days 11–12) — Apply what you've learned to your real project and make it stick.
Understanding Core Concepts
1. From Knowledge to Practice
You've learned the concepts over 11 days. But knowledge isn't practice. The difference is habits.
Habits are what you do without thinking—the default move when facing a problem. Building agent craft as a habit means: every time you ask an agent to work, you instinctively reach for a spec, not a prompt.
2. The Keystone Habit
One habit unlocks the others: write a spec before asking the agent.
Everything flows from this:
- Specs enable evaluation
- Evaluation enables iteration
- Iteration enables better results
If you do this one thing consistently, the rest follows naturally.
3. Friction Points
Building a habit means removing friction. If specs feel slow or formal, you won't write them.
Solution: keep them short. A spec doesn't need polish—it needs clarity. One paragraph of concrete criteria beats a polished but vague document.
4. Iteration on the Process Itself
As you build the habit, notice what works for you:
- Some people prefer specs as markdown files
- Others use a simple checklist
- Some add specs to existing ticketing systems
The format matters less than the consistency. Pick what fits your workflow and stick with it.
Tiny Action for Today (15–20 minutes)
Commit to agent craft for the next week. Here's the challenge:
Every time you ask an agent to work on something, before sending the prompt:
- Spend 5 minutes writing a one-paragraph spec
- Include: goal, inputs, outputs, 2–3 success criteria
- Compare the result to last week's approach
After one week, you'll notice the difference. The second run with a spec produces better output. That's the moment the habit clicks.
End of Series
You've completed Agent Craft. You now understand:
- Why evaluation matters (Day 1)
- How to spec work (Day 2)
- Why context is critical (Day 3)
- How to measure progress (Days 4–6)
- What to watch for (Days 7–10)
- How to apply this to real work (Days 11–12)
The rest is practice. Write specs, evaluate, iterate. Do that consistently and you move from "prompting and hoping" to agent craft—reliable, measurable, and compound improvement.
Go build.