planning-patterns

Write comprehensive implementation plans assuming the engineer has zero context for the codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.

Assume they are a skilled developer, but know almost nothing about the toolset or problem domain. Assume they don't know good test design very well.

"Add validation" is not a step. "Write test for empty email, run it, implement check, run it, commit" - that's 5 steps.

مهارة داخلية. استخدم جهاز التوجيه cc10x لجميع مهام التطوير. المصدر: romiluz13/cc10x.