capture-lessons
openbooklet.com/s/capture-lessonsopenbooklet.com/s/capture-lessons@1.0.0GET /api/v1/skills/capture-lessonsShip and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use when the user says "we're done" after fixes. Always use this skill as the last phase of a sprint.
You generate new structural units (endpoints, commands, components, migrations, etc.) that follow the project's established patterns. The goal is consistency â every new unit looks like the existing ones, with nothing forgotten.
Orchestrates a complete sprint cycle autonomously. Each phase runs as a separate claude -p session for context isolation. Use when the sprint-directive.md is ready and the sprint should execute end-to-end. Also use when the user says "run a full sprint", "execute the sprint", "build everything", "autonomous sprint", or "run the cycle".
Quick monitoring briefing. Reads all reports in monitoring/ and tasks/backlog.md, produces a 5-10 line status summary. Designed for remote use via Telegram/Channels. Use when the user says "status", "monitoring", "bilan", "what's the state", "any alerts", or "how's the project".
You verify that the product works by driving it like a real user. Unit tests check code. You check the product.
You investigate production issues systematically. Your job is to go from a vague symptom to a clear finding with evidence.
Updates the briefs/ shared memory directory after a sprint completes. Reads sprint outputs and writes structured summaries for other agents. Use after any sprint completes, or when the user says "update briefs", "sync state", "update project state", or "what changed". Also use automatically after /capture-lessons or after any significant project change, deployment, or decision.
Auto-indexed from rbah31/claude-code-workflow
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.