Integrate TDD and Grill with Docs into Design, Implementation, and Verification workflows
This commit is contained in:
+14
-1
@@ -11,6 +11,15 @@ Your job is to create a clear, actionable design for the project based on the sp
|
||||
|
||||
{task-description}
|
||||
|
||||
## Read These Files
|
||||
|
||||
1. {project}/tasks/{task-name}/SPEC.md
|
||||
2. {project}/.agent-framework/RULES.md
|
||||
|
||||
## Task
|
||||
|
||||
{task-description}
|
||||
|
||||
## Output
|
||||
|
||||
Produce a file called `DESIGN.md` at {project}/tasks/{task-name}/DESIGN.md containing:
|
||||
@@ -38,7 +47,11 @@ Produce a file called `DESIGN.md` at {project}/tasks/{task-name}/DESIGN.md conta
|
||||
- Biggest technical or product risks
|
||||
- Areas that need exploration or validation first
|
||||
|
||||
### 6. Non-Functional Requirements
|
||||
### 6. Documentation Plan
|
||||
- List all specific documentation that must be updated or created (e.g., README sections, API docs, docstrings).
|
||||
- Define the "source of truth" for each piece of documentation.
|
||||
|
||||
### 7. Non-Functional Requirements
|
||||
- Performance, security, reliability, or scale considerations (if relevant)
|
||||
|
||||
When the design is complete, output "CONTRACT_MET" and stop.
|
||||
|
||||
Reference in New Issue
Block a user