ehoandClaude Opus 5
12f17d9d73
Two backlog trees are complete: `docs/project/backlog/` (75 files, every WP done) and `docs/project/refactor-backlog-setup/` (the arc before it). Move both under `docs/project/archive/` with `git mv`, so history stays intact through `git log --follow`. `SHOWCASE-ROADMAP.md` moves with them, because it points at the now-archived backlog README. Add `docs/project/archive/README.md`. It states that these trees are historical and names the two directories that are still live. Repoint every inbound reference named in RD-30's Files table: CLAUDE.md, the root README, both backend READMEs, `LetterHtml.cs`, `a11y.mdx`, the `document-feature` and `new-ssp` skills, and the readable-codebase PLAN, README, and RD-19 ticket. Fix two upward-relative links inside the moved WP files (WP-68, WP-69) that gained a directory level and would otherwise break. Repoint `.prettierignore`'s two agent-prompt exclusions to their new path, so prettier keeps leaving those files' exact wording alone. Mark RD-30 done and check off its acceptance criteria; flip its README row to done. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
34 lines
1.4 KiB
Markdown
34 lines
1.4 KiB
Markdown
MODEL: Sonnet
|
|
OUTPUT: status update in /refactor-backlog/99-backlog.md +
|
|
/refactor-backlog/implementation/[ticket-id].md
|
|
DEPENDS ON: ticket status = not_started, no unresolved compliance/ADR-fix flag,
|
|
all tickets in "Depends on" column = implemented or needs_review
|
|
|
|
---
|
|
|
|
[Insert contents of _persistence-protocol.md here — scoped to one ticket, not a
|
|
module list]
|
|
|
|
AGENT: Implementation Agent
|
|
|
|
Input: one ticket from 99-backlog.md (fill in TICKET-ID below), the Phase 1
|
|
file(s) that produced it, and 00-baseline.md.
|
|
|
|
TICKET-ID: [fill in before dispatching this agent]
|
|
|
|
Scope discipline:
|
|
- Implement exactly the change described in the ticket. No scope expansion, no
|
|
incidental fixes.
|
|
- If the ticket is ambiguous or underspecified for implementation, do not guess —
|
|
write a blocker note to the ticket's status and stop.
|
|
- Do not modify architecture/pattern decisions (hexagonal boundaries, CQRS-light
|
|
structure) — those are Opus-level design calls already made in the ticket. If
|
|
implementation reveals the design call was wrong, flag back to Consolidation
|
|
rather than deciding unilaterally.
|
|
- Tickets touching a BIO2-flagged item are blocked until human compliance
|
|
sign-off is recorded in the ticket status — do not implement first and flag
|
|
after.
|
|
|
|
Update ticket status in 99-backlog.md: not_started → in_progress → implemented
|
|
→ needs_review. Append implementation notes to implementation/[ticket-id].md.
|