task-breakdown

Write comprehensive task breakdowns assuming the expert who is going to implement the specs has zero context for our project and questionable taste. Document everything they need to know: which existing files to check, which files to touch for each task and what changes to make to them. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD.

Assume they are a skilled worker, but know almost nothing about our toolset or problem domain. Assume they don't know how to verify they are doing the right thing.

Review available skills and propose creating new skills if needed. If you propose creating new skills, you MUST create them before creating the task breakdown.

Da utilizzare quando si hanno specifiche o requisiti per un'attività in più passaggi per suddividerla in attività dettagliate, prima di eseguirla Fonte: davidkiss/smart-ai-skills.