dev-playbooks 1.2.2 → 1.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -73,6 +73,16 @@ Main Plan Area writing rules (mandatory):
|
|
|
73
73
|
- Each task package must include: Purpose (Why), Deliverables, Impact Scope (Files/Modules), Acceptance Criteria, Dependencies, Risks.
|
|
74
74
|
- Subtasks should go up to interface/contract/behavior boundaries, not function bodies.
|
|
75
75
|
- Acceptance criteria must be observable and testable: specify which tests/acceptance checks to add/update and key metric thresholds.
|
|
76
|
+
- **Task checkbox format (required)**: each subtask must use Markdown task list format `- [ ]` to support Coder plan persistence.
|
|
77
|
+
- Initial state must be `- [ ]` (not done)
|
|
78
|
+
- Coder will update to `- [x]` (done) immediately after completing the subtask
|
|
79
|
+
- The subtask title must be on the checkbox line (do not replace it with `#### MPx.y:` headings)
|
|
80
|
+
- Example:
|
|
81
|
+
```markdown
|
|
82
|
+
### MP1: Task Package Name
|
|
83
|
+
- [ ] MP1.1 Subtask description
|
|
84
|
+
- [ ] MP1.2 Subtask description
|
|
85
|
+
```
|
|
76
86
|
|
|
77
87
|
Temporary Plan Area rules (mandatory):
|
|
78
88
|
- Only for off-plan high-priority tasks; include trigger reason, impact scope, minimal fix scope, regression test requirements.
|