Menu
Write changelog, update reference docs, archive completed workstream.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | release |
| description | Write changelog, update reference docs, archive completed workstream. |
| trigger | When qa-report.md exists with PASS verdict. |
| inputs | ["spec.md","plan.md","tasks.md","handoff.md","qa-report.md"] |
| outputs | [".agents-stack/workstream/<ws-id>_{YYYYMMDD}/changelog.md",".agents-stack/workstream/<ws-id>_{YYYYMMDD}/status.json","updated reference docs if needed"] |
| boundaries | Read-only except changelog.md, status.json, and reference/. Archive is move not copy. |
Close out a completed workstream. Read all artifacts, write the changelog, update project knowledge if needed, archive the workstream.
Read all workstream artifacts from .agents-stack/<id>/:
spec.md — original requirementsplan.md — planned architecturetasks.md — task breakdownhandoff.md — implementation evidenceqa-report.md — QA verdict (must be PASS)# Changelog
## Workstream
- ID: [WORKSTREAM-ID]
- Title: [title]
## Summary
[2-3 sentences: what was accomplished]
## Changes
| File | Change Type | Description |
|------|-------------|-------------|
| `src/file1.ts` | add | [brief description] |
| `src/file2.ts` | modify | [brief description] |
## Deviations from PLAN
| Planned | Actual | Rationale |
|---------|--------|-----------|
| [original approach in plan.md] | [what was actually done] | [why it changed] |
## Deployment Checklist
- [ ] Environment variables: [list additions/changes]
- [ ] Database migrations: [list migration files]
- [ ] Configuration changes: [list config changes]
## Reference Update Suggestions
- [ ] Update architecture.md: [what changed structurally]
- [ ] Update design.md: [what changed in design]
- [ ] No reference update needed
After writing changelog, assess whether this workstream produced lasting project knowledge:
.agents-stack/reference/architecture.md.agents-stack/reference/design.mdRule: reference/ is read-optimized. Only update for decisions that affect future workstreams. Not every workstream needs a reference update.
.agents-stack/<id>/ to .agents-stack/archive/<id>/.agents-stack/tracked-work.json:
active fieldparked or leave nullevidence_path to archive locationstatus.json before archiving: phase: "archived"changelog.mdtracked-work.jsonchangelog.md written. Reference updated (if needed). Workstream archived in .agents-stack/archive/. Ready for next workstream.
Use when a request will produce frontend UI, a visual asset, an image prompt, or a video prompt, AND the intent/style is not already fully specified by the user or an existing design system in the repo. Forces a minimal, checkable design-context object to exist before generation so output does not default to generic/templated. Do NOT use for: single-property edits (color, spacing, copy tweak) with no ambiguity; bug fixes; refactors; or when the user already gave complete visual specs and you only need to execute. For those, just do the work.
Root orchestrator. Reads durable state, routes to one phase, dispatches fresh workers.
Pre-implementation alignment gate. Checks spec / plan / tasks consistency and plan vs codebase reality before code is written.
Define the goal: what problem we solve, for whom, and what success looks like. The directional anchor that architecture and specs must serve.
RED-GREEN-REFACTOR implementation per task. Each task passes before next. Produces handoff.md with reproducible evidence.
Design architecture: components, API schema, DB model, impact analysis, test strategy.