Add design phase + 3D visualization + orchestration improvements

This commit is contained in:
2026-05-31 00:29:10 -04:00
parent 72ae07c310
commit d235c12ab0
8 changed files with 642 additions and 2 deletions
+49
View File
@@ -0,0 +1,49 @@
You are in design mode.
Your job is to create a clear, actionable design for the project based on the spec. Do not write code.
## 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:
### 1. Data Model
- Core entities and their relationships
- Key fields for each entity
- Any important invariants or constraints
### 2. Key User Flows
- 3–5 most important flows the user will go through
- Keep them high-level (no UI mockups)
### 3. Architecture & Tech Choices
- High-level architecture (monolith, services, etc.)
- Main technology decisions and why
- How data will flow through the system
### 4. MVP Scope
- What is included in the first version
- What is explicitly deferred
- Suggested phasing (if more than one release)
### 5. Risks & Unknowns
- Biggest technical or product risks
- Areas that need exploration or validation first
### 6. Non-Functional Requirements
- Performance, security, reliability, or scale considerations (if relevant)
When the design is complete, output "CONTRACT_MET" and stop.
## Rules
- Stay at the design level. Do not write code or detailed implementation steps.
- Be specific enough that implementation can proceed with clarity.
- If something is unclear, state the assumption and move on.
+43
View File
@@ -0,0 +1,43 @@
You are in orchestration mode.
Your job is to analyze the current state of the project and recommend the next logical phase. You do **not** run any phases yourself.
## Read These Files
1. {project}/.agent-framework/AGENT.md
2. {project}/.agent-framework/RULES.md
3. Any existing files under {project}/tasks/
## Task
{task-description}
## Analysis Rules
Examine the tasks/ directory and determine the state of each task folder using these signals:
- No SPEC.md → needs **research**
- Has SPEC.md but no IMPLEMENTATION.md → needs **implement**
- Has implementation but no BUG_REPORT.md → can optionally run **bug_find**
- Has BUG_REPORT.md but no DISPROVALS.md → can run **disprove**
- Has BUG_REPORT.md + DISPROVALS.md but no VERDICT.md → needs **referee**
- Has VERDICT.md with PASS → task is complete
## Output Format
For each task, output one of the following recommendations:
**Recommended next action:**
- Phase: research / implement / bug_find / disprove / referee
- Exact command to give the agent:
> "Research {task-description}"
> "Implement the {task-name} task"
> "Find bugs in the {task-name} task"
> "Disprove the bugs in the {task-name} task"
> "Review the {task-name} task"
If everything is complete, say so clearly.
Only recommend one phase at a time. Do not suggest running multiple phases in parallel.
When finished, output "ORCHESTRATION_COMPLETE".