Interviews you into a use-case document that an independent agent then reviews adversarially, breaks the feature down into commit-sized implementation plans, and executes them with subagents sized to each plan's complexity. Run /impl-flow:spec (design+plan) and /impl-flow:implement independently, or /impl-flow:all for the full pipeline in one go. For changes to something that already exists, /impl-flow:fix is a lighter fix mode that revises the existing use-case document and hunts for what a partial fix would leave behind.
Plugin impl-flow from marketplace ogawa929 in Ogawa929/ogawa929-claude-code-plugins. Commands read from the repo's manifest — 1 month ago.
/impl-flow:allRun the full impl-flow pipeline (design -> plan -> implement) in one invocation, with a single checkpoint after the plan is drafted before implementation begins
/impl-flow:designInteractively interview the user to nail down requirements for a new implementation, record them as a use-case document at the root of the task-set directory, and harden it through an adversarial review by an independent agent before feeding into the plan phase (Phase 1 of impl-flow: design -> plan
/impl-flow:diagnosePin down a bug or change request against an existing use-case document, find the root cause, revise the affected use cases, and hunt for what a partial fix would miss through a three-layer omission review (Phase 1 of impl-flow's fix mode: diagnose -> plan -> implement). Not a standalone command — on
/impl-flow:fixFix mode — diagnose a bug or revision against an existing use-case document, revise the affected use cases, plan the fix, and implement it, with a single checkpoint after the plans are drafted. Lighter than /impl-flow:all, and aimed at not missing anything a partial fix would leave behind.
/impl-flow:implementExecute the pending implementation plans in a task-set directory. The main session acts as leader and dispatches each plan to an implementation subagent sized to that plan's declared complexity, running independent plans in parallel within a single branch (Phase 3 of impl-flow: design -> plan -> imp
/impl-flow:planTurn a design (or direct requirements) into commit-sized implementation plan files, each self-contained enough to run in a brand-new Claude Code session (Phase 2 of impl-flow: design -> plan -> implement). Not a standalone command — only invoked via /impl-flow:spec or /impl-flow:all.
/impl-flow:specRun design then plan back to back in one invocation (no implementation) — the two phases that are almost always used together
implementer-deepExecutes one high-complexity impl-flow implementation plan (real design judgement required while implementing) on opus at xhigh effort. Dispatched by /impl-flow:implement based on the plan's declared complexity — not for general-purpose work.
implementer-lightExecutes one low-complexity impl-flow implementation plan (mechanical, well-scoped edits) on sonnet at medium effort. Dispatched by /impl-flow:implement based on the plan's declared complexity — not for general-purpose work.
implementer-standardExecutes one medium-complexity impl-flow implementation plan (new code in an existing pattern) on sonnet at high effort. Dispatched by /impl-flow:implement based on the plan's declared complexity, and used as the fallback when a plan declares no complexity — not for general-purpose work.
A configurable Claude Code status line: model, directory, git branch, context usage bar, cost, session duration and more, in one to three lines. Run /statusline-pack:setup to install a preset into ~/.claude and wire up settings.json, hand-edit ~/.claude/statusline-pack.json to change the segments, and /statusline-pack:restore to put your previous status line back.
2 commands
An auto-triggered skill for draw.io / diagrams.net files that enforces human-readable layout: no overlapping shapes, edges or labels, text that fits inside its shape, categories shown through both colour and position, and a canvas enlarged to fit the content instead of the content squeezed to fit the canvas. Ships a validator script that checks the generated XML, and per-notation rules for ER, sequence, state, network and class diagrams.
1 skill
An auto-triggered skill that applies a house commit convention: prefix-tagged subjects (feat/fix/docs/refactor/chore/revert), a 50-character noun-phrase summary with no trailing period, What in the subject and Why in the body, and revert-safe commit granularity. Follows the repository's existing commit language.
1 skill
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.