Claude Skills · Writing & Editing
Hyper Recap
zeikar/hyperclaudeUse at cycle completion to write a human-readable recap of what was built and why — "recap this cycle", "summarize what we built", "cycle recap", "write up what changed this cycle". Also when the user invokes /hyperclaude:hyper-recap. Claude-only — no Codex, no agent dispatch — runs after a plan is implemented and reviewed, and writes a recap to .hyperclaude/recaps/. Recaps ONE completed detailed plan / milestone archived under .hyperclaude/plans/done/. Distinct from /hyperclaude:hyper-memory (durable knowledge extraction, not a one-cycle narrative).
At a glance
This skill is for Writing & Editing and helps you write a cycle recap, summarize completed work, and document what was built this cycle.
/plugin marketplace add zeikar/hyperclaude
/plugin install hyper-recap
Setup, runtime and requirements describe zeikar/hyperclaude, the repo this skill ships in.
HyperclaudeCycle CompletionProject DocumentationNarrative SummaryMilestone Tracking
Also in zeikar/hyperclaude
View the repoUse when plan-harden → implement-harden should chain in one gesture — hyper-plan-loop produces a clean plan, then hyper-implement-loop execu...
Use after producing code changes that should be critiqued — before commit or merge. The default for a natural-language code review of the us...
Use when encountering a test failure, exception, regression, or unexpected behavior — before proposing fixes. Also when the user invokes /hy...
Use when documentation should be brought into accuracy with the code in one gesture — Codex docs-review → fix → re-review, repeated until no...
Use after documentation edits — typically after the documenter agent runs, or when the user invokes /hyperclaude:hyper-docs-review. Runs Cod...
Use after implementation changes documented API, schemas, CLI flags, or architecture — before docs go stale. Also when the user invokes /hyp...
Use when about to execute a multi-task plan from .hyperclaude/plans/. Also when the user invokes /hyperclaude:hyper-implement. Runs each tas...
Use when a plan should be executed end-to-end and critic-hardened in one gesture — implement → Codex code-review → fix, repeated until clean...
Use when starting from a vague or under-specified idea and want requirements clarified before planning — "interview me", "ask me what you ne...
Use on-demand to extract evidence-anchored repo-local knowledge candidates from accumulated .hyperclaude/ artifacts (plans/done, plan-review...
Use when about to start a non-trivial implementation that needs decomposition before coding. Also when the user invokes /hyperclaude:hyper-p...
Use when a plan should be produced and critic-hardened in one gesture — plan → Codex review → revise, repeated until clean. Also when the us...
Other Writing & Editing skills
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical s...
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improv...
Writing, exploit — shape raw material into an article, paragraph by paragraph.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Writing, exploit — assemble raw material into a journey of beats, grounding each term before a beat leans on it.
Writing, explore — mine raw fragments, no structure yet.