oscaner-skills plugin
The kairos plugin and the cdd engine carry a code change from design to close in small verifiable steps with review.
- 66 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The engine is fetched through npx and runs agent work rounds in your repository.
- Upstream plugins are installed at their current version.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/oscaner-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The engine is fetched through npx and runs agent work rounds in your repository.
- Upstream plugins are installed at their current version.
This is third-party code. Review the repository files before installing.
What it does
The repository ships a continuous-discovery development methodology, cdd, as a set of plugins. The first plugin, `kairos`, holds six `cdd-*` skills: orchestrators for design, planning and closing a change, plus `cdd-report` for filing what the session itself got wrong. The `cdd` command handles pre-flight gates, the plan ledger, round records and a progress board. The loop has three modes: `implement` executes the brief, `review` judges the result against fixed criteria and `fix` applies the findings. Every finding carries a blocker, warn or nit severity, so one closing rule covers all review types. `cdd init` installs `kairos` and two upstream sets, `superpowers` and `mattpocock-skills`.
Who it is for. Developers who run code changes through an agent and want shared rules for planning, review and closing.
Good fit when
- A large change is cut into task groups and each passes review against common criteria.
- A blocking finding goes back for a fix and then for a re-review.
- A project is set up for Claude Code or Pi with one `cdd init` command.
- Mistakes made by the session itself are filed with `cdd-report`.
Not a fit when
- You need one light skill rather than a whole discipline with an engine.
- Your team prefers to plan upfront and fix it in a document.
- Company policy forbids third-party plugins while `cdd init` installs `superpowers`.
Example request
Run cdd-design for the task of adding CSV report export and drive the change through implement, review and fix rounds.Limitations
Verified on Claude Code and Pi, and the README confirms no other hosts. `cdd init` installs three plugins in order through the host's own commands and takes the upstream sets at their current version, so their behaviour changes with the authors' releases. The skills fetch the engine through `npx -y` on demand, which means they reach the npm registry while working. Start the first run with `/kairos:cdd-design` and follow the engine `next:` line from there.
How to disable. Remove the plugins with your host commands, for example `claude plugin uninstall`, and clean the `cdd` working records in the repository.
FAQ
What does cdd init install?
Three plugins in order: `kairos` from the author, then `superpowers` and `mattpocock-skills` from their publishers.
How do I update the install?
Re-run `init` with `--update`. The `--include-recommends` flag adds six capability packages for pi.
What is the implement, review, fix loop?
The executor performs the brief, review checks the result against criteria and fix applies the findings. A blocked review goes back for a fix and a re-review.
What severity levels exist?
A blocker routes to a fix and a re-review, warn and nit close as `REVIEW_FIX`, and zero findings close at once.
Where do I start after installing?
Call `/kairos:cdd-design` and follow the `next:` line in the engine output.
Discussion
No questions or reviews yet.
Related
PluginsNick Tune's plugin marketplace for Claude Code: checks before a task is handed in, code review and TDD personas
A Codex plugin that runs Claude Code for reviews, rescue tasks and tracked background jobs without leaving Codex
A plugin that readies a project for Claude Code: guidance, tests, review, TDD, refactoring and a resumable fix loop
cc-thingz: Claude Code plugins
cc-thingz
A personal toolkit as a marketplace: seven independent Claude Code plugins for planning, review, releases and a backlog
22 skills for the full Claude Code project lifecycle: setup and task scope, code review, pre-push checks and session notes.
A Claude Code plugin for large specs: requirements with proof obligations, a walking skeleton and audited sprints
README in short
The README lays out the cdd methodology and a five-stage change flow from design to close. Install is one engine command and the rest loads as work proceeds.