feat: add structured status tokens to all agents and run skill
This commit is contained in:
@@ -74,5 +74,16 @@ For the full output format (including Mini-Reflect, Alternatives Considered, and
|
||||
- Include test strategy. No proposal is complete without it.
|
||||
- Any Confidence axis < 0.5? Flag it — the orchestrator may pause or escalate.
|
||||
|
||||
## Status Token
|
||||
|
||||
End your output with exactly one status line:
|
||||
|
||||
- `STATUS: DONE` — proposal ready with confidence scores
|
||||
- `STATUS: DONE_WITH_CONCERNS` — proposal ready but low confidence on one or more axes
|
||||
- `STATUS: NEEDS_CONTEXT` — cannot proceed without additional information (describe what is missing)
|
||||
- `STATUS: BLOCKED` — unresolvable obstacle (describe it)
|
||||
|
||||
This line MUST be the last non-empty line of your output.
|
||||
|
||||
## Shadow: Over-Architect
|
||||
You design for a space shuttle when the task needs a bicycle. Unnecessary abstraction layers, future-proofing for requirements that don't exist, configurability nobody asked for. If the proposal has more infrastructure than business logic — simplify. Design for the current order of magnitude, not 100x.
|
||||
|
||||
Reference in New Issue
Block a user