name: okf-adr-review description: Accept or reject a proposed ADR at the owner's direction — status flip, reversal per rollback trigger, index and log updates. Use when the owner reviews pending decisions, says to accept/reject an ADR, or asks what's awaiting review.
ADR review mechanics
The owner finds pending decisions with bash scripts/okf pending (the SessionStart hook also reports the count). The decision is the owner's; the edits can be yours at their direction.
Accepting an ADR:
- Flip
status: proposedtostatus: acceptedin the frontmatter, and update the body# Statussection (date, "at the owner's direction"). - Remove any "(proposed)" markers the ADR carries in the ADR index entries (
docs/adr/index.mdby default; alayout:block indocs/okf-map.ymlmay relocate it),docs/GOAL.mdmilestones, or the current-state line ofCLAUDE.md. - No implementation change is usually needed: under the propose-then-implement policy the work already exists — acceptance makes it binding for future work.
- Add a dated
docs/log.mdentry recording the acceptance, and verifybash scripts/okf pendingno longer lists it.
Rejecting an ADR:
- Revert the work built on it, per the ADR's own rollback / revisit trigger section — that section names what reverting takes.
- Either delete the ADR file and its index entry, or keep it with a
status: rejectednote recording why, per the owner's preference. - Run the repo's test command after the reversal; a broken revert is not a completed rejection.
- Log the rejection and the reversal scope in
docs/log.md.
Requested changes (neither accept nor reject): treat the owner's comments as a task — amend the ADR and the implementation together, keep status: proposed, and flag it again in the summary.
The pending scan reads frontmatter status: first, then the body conventions brownfield repos use (a - Status: X bullet or a ## Status section). ADRs with none of those are invisible to it — add frontmatter status to them when found, as a formatting-only fix; frontmatter stays the preferred form for new ADRs.
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Hono Documentation Search
Documentation
Use the hono CLI to search and view Hono framework documentation. It provides commands like hono search and hono docs to quickly find and browse documentation directly from the terminal. This is useful when developing with Hono and needing instant access to API references or guides.