Remove loop-build harness and associated configuration files.
This commit is contained in:
63
loop-build/prompts/planner.md
Normal file
63
loop-build/prompts/planner.md
Normal file
@@ -0,0 +1,63 @@
|
||||
# loop-build Planner Prompt
|
||||
|
||||
## Inputs
|
||||
|
||||
- `goal`: user goal for the task
|
||||
- `constraints`: hard constraints and guardrails
|
||||
- `repo_context_hint`: optional repo context (size, language, architecture, risk areas)
|
||||
- `current_state_summary`: optional summary from previous run
|
||||
|
||||
## Task
|
||||
|
||||
Generate a strict JSON object for `TASKS` creation only (no implementation code).
|
||||
|
||||
Output MUST be valid JSON with these top-level fields:
|
||||
|
||||
- `task_id`
|
||||
- `goal`
|
||||
- `constraints`
|
||||
- `plan_steps`
|
||||
- `success_criteria`
|
||||
- `risk_notes`
|
||||
- `required_files`
|
||||
- `verify_targets`
|
||||
|
||||
Each element in `plan_steps` must include:
|
||||
|
||||
- `step_id`
|
||||
- `action`
|
||||
- `verification`
|
||||
- `rollback`
|
||||
- `risk_level`
|
||||
- `expected_output`
|
||||
|
||||
Use only 3~7 steps.
|
||||
|
||||
## Output format (example)
|
||||
|
||||
```json
|
||||
{
|
||||
"task_id": "task-2026-001",
|
||||
"goal": "...",
|
||||
"constraints": ["..."],
|
||||
"plan_steps": [
|
||||
{
|
||||
"step_id": "1",
|
||||
"action": "Read minimal context and add patch for file X",
|
||||
"verification": "unit",
|
||||
"rollback": "git checkout -- fileX || git checkout .",
|
||||
"risk_level": "LOW",
|
||||
"expected_output": "Target test starts passing or diff is constrained."
|
||||
}
|
||||
],
|
||||
"success_criteria": ["..."],
|
||||
"risk_notes": ["..."],
|
||||
"required_files": ["path/to/file1", "path/to/file2"],
|
||||
"verify_targets": ["unit", "lint"]
|
||||
}
|
||||
```
|
||||
|
||||
Rules:
|
||||
- Do not return implementation code or full diffs.
|
||||
- Keep each step actionable and minimal for one-step incremental execution.
|
||||
- One step must map to one incremental change and one verification check.
|
||||
Reference in New Issue
Block a user