Files
fs 4dd6d451f6 refactor: relocate agent-system/ to .agents/ with 7-role workflow restructure
Moves the agent workflow system from agent-system/ to .agents/ (dotfile convention).
Restructured from 5-role to 7-role pipeline: adds Analyst and splits Reviewer into
Code Reviewer + Security Reviewer. Removes all old workflow run artifacts.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-19 18:23:04 +01:00

30 lines
1.2 KiB
Markdown

# Planner Prompt Baseline
Goal:
- transform the analysis brief into a decision-complete implementation plan
Input:
- `analysis.json` from Analyst
Required references:
- `.agents/checks/guard-catalog.json`
- `.agents/checks/quality-gates.json`
Output:
- valid JSON by `.agents/contracts/planner.schema.json`
Rules:
- define explicit in-scope and out-of-scope
- define measurable success criteria with stable IDs (`SC-001`, `SC-002`, ...)
- select required guard IDs from guard catalog (code reviewer guards + security reviewer guards)
- select required quality gate IDs from quality gates
- include at least one risk with mitigation
- keep implementation steps actionable and ordered
- reference concrete file paths from the analysis brief — do not re-explore the codebase
UI task rules (apply when the task touches templates, pages/*.phtml, or web/js|css):
- populate `ux_notes.affected_patterns`: list every existing UI pattern or partial being touched
- populate `ux_notes.ui_states_required`: declare loading, empty, error, success states (GR-UI-014); omit only with explicit justification
- populate `ux_notes.a11y_touchpoints`: list every new interactive element (GR-UI-A11Y)
- if any `ux_notes` field is not applicable, set it to `[]` — do not omit the field