Plugin · Claude Code · Automation

Inakam Continuous Dev Cycle

inakam-continuous-dev-cycle is a Claude Code plugin for the Operate phase that runs a self-sustaining continuous planning and execution development cycle with automated progress.

by inakam · github.com/inakam/continuous-dev-cycle

Register a continuous development cycle plugin that autonomously plans, proposes expansions, executes work, and commits progress in a looping workflow.

0
GitHub stars
0
Installs
0
Community votes
One vote per signed-in builder - it helps surface the tools the community actually relies on.
Install

Add it to Claude Code

Install the plugin in Claude Code. One command, paste-ready.

Install the plugin
/plugin install inakam-continuous-dev-cycle@inakam/continuous-dev-cycle
Add to ClaudeUse the Agent APISkillselion is itself an MCP server - your agent can fetch this config directly.
Agent API

Built to be called by your agent

Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.

Retrieve this entry with skillselion.get_details("plugin:inakam/continuous-dev-cycle") and the paste-ready config with skillselion.get_install_config("plugin:inakam/continuous-dev-cycle").

About

What it does

inakam-continuous-dev-cycle is a single-plugin Claude Code offering for solo builders who want the agent to own more of the plan–execute–commit rhythm instead of stopping after one response. It emphasizes a continuous development cycle: planning artifacts feed proposals, the loop executes tasks, integrates progress, and can expand scope when the model identifies follow-on work—language in the catalog points at Ralph-loop and planning-with-files style automation. That makes it useful when you are iterating a codebase for weeks, running agent-led refactors, or trying to keep momentum without manually re-prompting every step. It is intermediate to advanced because you must trust autonomous commits, define guardrails, and review diffs regularly. It is less suited as a substitute for human product discovery or formal QA gates. Pair it with your own review practices in Ship before you treat the loop as production-ready.

Highlights

  • 1-plugin bundle focused on continuous autonomous planning and execution
  • Integrates planning-with-files style plans with executable agent progress
  • Ralph-loop / self-sustaining cycle that proposes expansions and follows through
  • Automatic commits and progress tracking across repeated dev iterations
  • Designed to run development cycles continuously rather than single-shot prompts

Why builders use it

Solo builders lose hours re-seeding context and re-prompting agents after each small win, so ambitious backlogs stall between sessions.

After install, Claude Code can loop through plan proposals, execution, expansions, and commits so iteration continues with less manual orchestration.

At a glance

  • Type - Plugin in Automation.
  • Adoption - 0 installs, 0 stars, 0 votes.

FAQ

Who is inakam-continuous-dev-cycle for?

Solo and indie builders using Claude Code who want long-running autonomous planning and execution instead of discrete single-turn coding tasks.

When should I use inakam-continuous-dev-cycle?

Use it when you have an active codebase and want the agent to continuously plan, execute, propose expansions, and record progress across sessions.

How do I add inakam-continuous-dev-cycle to my agent?

Add the plugin from inakam/continuous-dev-cycle in Claude Code, configure your repo and planning files, then start the continuous cycle skill per the repository README.

Discussion

Comments

Share how you use inakam-continuous-dev-cycle, gotchas, or tips for other indie builders.

No comments yet - be the first to share how you use it.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.