29 lines
1.4 KiB
Markdown
29 lines
1.4 KiB
Markdown
# Planner Prompt Baseline
|
|
|
|
Goal:
|
|
- transform issue input into a decision-complete plan
|
|
|
|
Required references:
|
|
- `tools/codex-skills/starterkit-planner/SKILL.md`
|
|
- `tools/codex-skills/core-guardrails/SKILL.md`
|
|
- `tools/codex-skills/starterkit-grid-standards/SKILL.md` (for UI/list tasks)
|
|
- `agent-system/checks/guard-catalog.json`
|
|
- `agent-system/checks/quality-gates.json`
|
|
|
|
Output:
|
|
- valid JSON by `agent-system/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
|
|
- select required quality gate IDs from quality gates list
|
|
- include at least one risk with mitigation
|
|
- keep implementation steps actionable and ordered
|
|
|
|
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 (e.g. "app-details-titlebar", "initStandardListPage")
|
|
- populate `ux_notes.ui_states_required`: declare all four states that the new view/component must handle — loading, empty, error, success (GR-UI-014); omit only with explicit justification
|
|
- populate `ux_notes.a11y_touchpoints`: list every new interactive element and confirm it will be keyboard-operable and use semantic HTML (GR-UI-013)
|
|
- if any item in `ux_notes` is not applicable, set it to an empty array `[]` — do not omit the field
|