Implement
Spec-Driven Agentic OS for Claude Code + OpenAI Codex CLI. Native skills, subagents, hooks, and an adversarial codex review loop. Inspired by github/spec-kit, built on Claude Code primitives. No daemon, no vendor lock-in.
npx -y skills add MakFly/ai-dev-kit --skill implementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use PROACTIVELY when the user invokes /implement <slug> or asks "now build it / run the tasks / execute the plan". Runs the `implementer` subagent in a forked context which walks specs/<slug>/tasks.md and writes src/** + tests/** one task at a time, one commit per task.
SKILL.md
1.9 KB, as published. Nobody here has run it
/implement
Execute specs/<slug>/tasks.md task-by-task via the implementer subagent.
Procedure
- Read tasks. Parse tasks.md. Identify the next un-
[x]task respecting dependencies. - Pre-flight.
- Verify spec.md
Status: locked(orclarifiedat minimum). - Verify plan.md
Status: reviewedorlocked. - Verify clean working tree:
git status -smust be empty.
- Verify spec.md
- Delegate per task. Invoke
implementerfor ONE task. Wait for it to mark[x]and commit. Then next. - Stream progress. After each task, print to chat: task ID, files changed, test command result.
- Stop conditions.
- All tasks
[x]: print "✓ all tasks complete", suggest/review <slug>. - Implementer fails: print failure detail, do NOT auto-skip — ask user.
- User interrupts: clean state, leave tasks.md in current state.
- All tasks
Flags
--from T<N>: resume from task N, skip already-[x]tasks before.--only T<N>,T<M>: run only listed tasks (and verify their dependencies are[x]).
Doctrine
- One task, one commit, one verify. No batching.
- Hook will block edits without spec. That's by design (cf rules/spec-before-code.md).
- No "while I'm here". Drift from the task scope is forbidden — the rule kicks in.
Pipeline position
... → /tasks → /implement [YOU] → /review