writing-plans

SKILL.md

Write comprehensive implementation plans assuming the engineer has zero context for our 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 our toolset or problem domain. Assume they don't know good test design very well.

Announce at start: "I'm using the writing-plans skill to create the implementation plan."

Verwenden Sie diese Option, wenn Sie eine Spezifikation oder Anforderungen für eine mehrstufige Aufgabe haben, bevor Sie mit dem Code in Berührung kommen Quelle: poletron/custom-rules.

Original anzeigen