> Spec-driven development is becoming the primary driver of code generation. This sounds like my current "phase" of AI coding. I have had so many project ideas for years that I can just spec out, everything I've thought about, all the little ideas and details, things I only had time to think about, never implement. I then feed it to Claude, and watch it meet my every specification, I can then test it, note any bugs,…
I am going lower level - every individual work item is a "task.md" file, starts initially as a user ask, then add planning, and then the agent checks gates "[ ]" on each subtask as it works through it. In the end the task files remain part of the project, documenting work done. I also keep an up to date mind map for the whole project to speed up start time. And I use git hooks on the tool event to print the current o…
```
"hooks": {
"PostToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "mix format ${file} 2>/dev/null || true"
}
]
}
],
"TaskCompleted": [
{
"matcher": "",
"hooks": [
{
"type": "prompt",
"prompt": "reminder: run mix test if implementation is complete"
}
]
}
],
"Stop": [
{
"hooks": [
{
"type": "prompt",
"prompt": "Check if all tasks are complete. If not, respond with {\"ok\": false, \"reason\": \"what remains to be done\"}."
}
]
}
]
},
Just update it to iterate over your file. It should be a little easier to manage than git hooks and can hammer in testing.