58 lines
3.0 KiB
Markdown
58 lines
3.0 KiB
Markdown
|
# Shared Revision Prompt Template
|
||
|
|
|
||
|
|
> Canonical prompt for spawning the {ROLE} (Worker) that revises artifacts
|
||
|
|
> between review rounds. Read on-demand by the Orchestrator in Phase C. The
|
||
|
|
> Orchestrator substitutes skill-level constants before dispatch.
|
||
|
|
|
||
|
|
```
|
||
|
|
Read `{TASK_FILE}` for your input files. {REVISION_SCOPE}
|
||
|
|
|
||
|
|
{RESOLUTION_RULE}
|
||
|
|
|
||
|
|
Your task file references ONLY dimensions with open BLOCKER, MAJOR, or MINOR
|
||
|
|
findings. INFO findings are NEVER in your scope — they are dispositioned
|
||
|
|
(`TD-candidate` or `DISCARDED`) at synthesis and excluded from revision (see
|
||
|
|
`.octopus/skills/_shared/review-pipeline-phases.md` Phase D, "Severity
|
||
|
|
handling — INFO disposition"). Do NOT act on or chase INFO observations.
|
||
|
|
|
||
|
|
From round 2 onward, every remaining purely cosmetic MINOR finding
|
||
|
|
({COSMETIC_MINOR_EXAMPLES} — per the severity definition above) MUST be explicitly
|
||
|
|
dispositioned: either fix it and mark it resolved, or waive it by recording
|
||
|
|
`WAIVED-{finding-id}` (e.g. `{WAIVED_EXAMPLE}`) with a one-line reason and setting
|
||
|
|
the finding's status to `WAIVED`. Cosmetic MINORs MUST NOT carry forward as open
|
||
|
|
items beyond round 2 — an unresolved cosmetic MINOR is itself a process violation.
|
||
|
|
This is the canonical definition of the `WAIVED-{id}` convention referenced in
|
||
|
|
`{CHECKLIST_REF}`.
|
||
|
|
|
||
|
|
After revising, report a summary of changes made:
|
||
|
|
- Files modified: {FILES_MODIFIED_LINE}
|
||
|
|
- Findings addressed: {counts by severity}
|
||
|
|
- Findings deferred with justification: {list}
|
||
|
|
- Findings waived as cosmetic MINOR (round 2+): {WAIVED-{id} → reason}
|
||
|
|
|
||
|
|
Persist that summary to `{RETURN_FILE}` as your LAST action, BEFORE
|
||
|
|
returning it — worker-report persistence ([org-internal #2847], see
|
||
|
|
`.octopus/skills/_shared/worker-report-persistence.md`). The persisted copy
|
||
|
|
is the report of record; if your completion notification is lost, the
|
||
|
|
Orchestrator recovers the revision outcome from this file.
|
||
|
|
```
|
||
|
|
|
||
|
|
## Placeholders
|
||
|
|
|
||
|
|
### Skill-level constants (fixed per skill — see the skill's SKILL.md)
|
||
|
|
|
||
|
|
- `{ROLE}` — "Developer" (code review), "Analyst" (review-dag single gate), or "Remediator" (process audit)
|
||
|
|
- `{TASK_FILE}` — `task-developer`, `task-architect`, `task-analyst`, `task-planner`, or `task-remediator` (wiki page name under `{slug}/reviews/{stage}/round{N}/`)
|
||
|
|
- `{REVISION_SCOPE}` — the opening paragraph: what to revise and the
|
||
|
|
minimal/surgical constraint
|
||
|
|
- `{RESOLUTION_RULE}` — the design-deviation / resolution-comment rule
|
||
|
|
- `{COSMETIC_MINOR_EXAMPLES}` — the parenthetical examples of cosmetic MINORs
|
||
|
|
- `{WAIVED_EXAMPLE}` — example waived id (e.g. `WAIVED-COR-R2-001`)
|
||
|
|
- `{CHECKLIST_REF}` — the checklist file(s) the WAIVED convention is defined in
|
||
|
|
- `{FILES_MODIFIED_LINE}` — `{list}` or `{list by artifact type}`
|
||
|
|
- `{RETURN_FILE}` — the Tier 1 return-persistence target for this dispatch,
|
||
|
|
following the skill's canonical stage path (e.g. review-code:
|
||
|
|
`.octopus/runs/{slug}/reviews/code/round{N}/revision-return.md`); default
|
||
|
|
per convention: `.octopus/runs/{slug}/workers/{chunk-id}-worker-{seq}.md`,
|
||
|
|
lightweight fallback `/tmp/octopus/{chunk-id}-worker-{seq}.md`
|