Skip to content

CDev v0.1.0 — first public release

Choose a tag to compare

View all tags
@elmayii elmayii released this 15 Aug 18:40
· 17 commits to main since this release
v0.1.0
4ce5151

What CDev is

Continuous Development Framework for Coding Agents. Coding agents work in sessions; CDev turns those sessions into continuous development: the repository — not the conversation — holds the plan (SPRINTS.md), the state (AGENT_PROGRESS.md) and the proof (git + recorded evidence). Any session resumes by reading, never by remembering.

What this release includes

  • Seven skills, namespaced cdev:*:
    • /cdev:bootstrap — condition one repository (recognition-first, structure + clarity halves, single human gate)
    • /cdev:cdev — the execution loop (dispatcher + one loop reading role profiles)
    • /cdev:cdev-planner — materialize an objective into batches, or gap-analyze
    • /cdev:ockham — re-tell dense technical output in plain language (user-invoked only)
    • /cdev:bootstrap-monorepo, /cdev:cdev-monorepo-planner, /cdev:cdev-monorepo — the optional multi-repo orchestration layer
  • Role profiles (profiles/): backend and frontend — each exactly four things: what verified means, what evidence means, the hardest gate, the self-chosen work order.
  • Conditioning templates (templates/) with a placeholder contract.
  • The method's documentation (docs/01–08): origin, model, mechanics, skills, two field reports, core-vs-periphery, installation.

Current binding

Designed as a coding-agent-independent method. Currently shipped as a Claude Code plugin — the first host binding.

Install

/plugin marketplace add elmayii/cdev-marketplace
/plugin install cdev@cdev-marketplace

Known limitations

  • One host binding (Claude Code); no other agent validated yet.
  • Field evidence comes from one product — deep (six weeks, five CDev instances, four repository kinds), but one. Second-product validation is the next phase.
  • Support scripts are PowerShell.
  • No fullstack profile — deliberately, until something real runs on one.

Experimental

The multi-repo orchestration layer ran nine days in production and broke in instructive, documented ways (docs/06); its five field-derived rules are new in this release and not yet re-validated in the field.

Assets 2
Loading