Skip to main content
command CX Codex

develop · rohitg00 — Claude Code command: what it does, how to install

Runs structured feature development through research, planning, testing checkpoints, and strict verification before committing.

MIT ★ 2,966 updated 2026-09-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow
Open on GitHub

What develop does

The command guides feature work through sequential gates. During the initial research phase, the agent inspects the codebase and grades readiness on a 100-point scale across five criteria: scope clarity, pattern familiarity, dependencies, edge cases, and test strategy. If the score stays below 70, the agent gathers more context instead of touching code.

Next comes an explicit plan covering modified files, new files, approach rationale, and verification steps. Implementation begins only when you respond with "proceed" or "approved". While coding, tests run after each file edit, with a forced pause for review every 5 changes.

The final review phase mandates a full re-read of every altered file. The agent greps for console.log, TODO tags, and hardcoded secrets, dropping any issue it cannot cite with an exact line number. Once verified, it formats a conventional commit and records project learnings in [LEARN] format.

What it helps with

  • break large features into gated research and planning phases
  • prevent untested code changes with per-file test runs
  • catch forgotten debug logs and unverified warnings before git commit
  • record implementation takeaways in a structured learning format

Example prompts for the agent

  • /develop add GitHub OAuth login flow
  • /develop migrate session store to Redis
  • /develop implement paginated CSV export for invoices

How to install develop

1Plugin marketplace

/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow

2Manually: put the files in place

.claude/commands/develop.md

Call it with /develop. For all projects use ~/.claude/commands/

Questions about develop

How to install develop in Claude Code?

Add the marketplace source with /plugin marketplace add rohitg00/pro-workflow, then run /plugin install pro-workflow@pro-workflow. You can also place the command file directly at .claude/commands/develop.md.

What does the develop command do?

It enforces a phased workflow (Research, Plan, Implement, Review & Commit) that requires passing confidence scores and explicit approval before any code changes occur.

When does the agent actually start writing code?

Implementation starts only after the research score reaches 70 or higher, the written plan is presented, and you explicitly type "proceed" or "approved".

Source text

develop.md · MIT
---
description: Build a feature using Research > Plan > Implement phases
argument-hint: <feature description>
---

# /develop - Multi-Phase Feature Development

Build features through structured phases with validation gates.

## Feature: $ARGUMENTS

### Phase 1: Research

Explore the codebase to understand the scope:

1. Find all relevant files and existing patterns
2. Check dependencies and constraints
3. Score confidence across 5 dimensions (0-100)

**Scoring:**
- Scope clarity (0-20): Know exactly what files change?
- Pattern familiarity (0-20): Similar patterns exist?
- Dependency awareness (0-20): Know what depends on changed code?
- Edge cases (0-20): Can identify the edge cases?
- Test strategy (0-20): Know how to verify?

**Decision:**
- Score >= 70 → Present research findings and move to Phase 2
- Score < 70 → Identify gaps, gather more context, re-score

### Phase 2: Plan

Present a plan for approval:

```text
PLAN: [Feature Name]

Goal: [one sentence]

Files to modify:
1. path/file.ts - [what changes]

New files:
1. path/new.ts - [purpose]

Approach:
1. [step with rationale]

Risks:
- [potential issue and mitigation]

Test strategy:
- [how to verify]
```

**Wait for "proceed" or "approved" before continuing.**

### Phase 3: Implement

Execute the approved plan:

1. Make changes in plan order
2. Run tests after each file change
3. Pause for review every 5 edits
4. Run full quality gates at the end (lint, typecheck, test)

### Phase 4: Review & Commit

Self-review with verification — every finding must be confirmed by reading the code.

1. **Read every changed file** — re-read each modified file in full
2. **Verify, don't assume** — for each potential issue, quote the exact line. If you can't quote it, drop the finding.
3. **Grep for problems** — run `grep` for console.log, TODO, hardcoded secrets, debug statements. Report only what grep finds.
4. **Never report unverified findings** — don't say "ensure X" or "consider Y". Either it's a confirmed problem with a file:line citation, or it's not worth reporting.
5. Present verified summary for final approval
6. Commit with conventional message

### Learning Capture

After completing, ask:
- What corrections were made during implementation?
- Any patterns worth adding to LEARNED?
- Format: `[LEARN] Category: Rule`

© Rohit Ghumare · MIT · rohitg00/pro-workflow

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

develop by other authors comes first.

develop coco-research develop runs a multi-agent build and bugfix pipeline that shards file edits across specialized agents and validates changes with regression evidence. CX Codex +1 ★ 328repo stars gitnexus-lfg abhigyanpatwari gitnexus-lfg runs the GitNexus engineering pipeline from initial planning to final review. Ideal when handling medium or large coding tasks that require an explicit sign-off checkpoint. CX Codex +1 244installs afk jakubkrehel afk is a Claude Code skill that inspects your repository while you are away, implements verified improvements on a dedicated branch, and writes a concise report. CX Codex +1 3,900installs ce-work EveryInc ce-work — a skill for Claude Code, Codex, Cursor, and other coding platforms that takes a plan, specification, or work description and runs implementation from start to finish—writing code in phases, verifying each locally. CX Codex +1 3,900installs swarm-implement ZaxbyHub swarm-implement runs feature work, bug fixes and refactors through a swarm workflow: parallel exploration, a scoped plan, then reviewer and critic passes on the diff. CX Codex +1 ★ 539repo stars ai-first-engineering affaan-m ai-first-engineering sets team process, review gates and architecture rules for codebases where AI agents produce most of the implementation. CX Codex +1 6,300installs kk serpro69 kk — a workflow plugin that carries an AI assistant from design through review, tests and docs, with a permission guard on the side. CX Codex ★ 155repo stars

From the same set83

The whole set →
auto-setup The auto-setup skill detects your project type and automatically configures linters, type checking, tests, and formatting. Use it when starting work on an unfamiliar codebase. CX Codex +1 ★ 2,966repo stars wiki-query wiki-query queries local markdown wikis indexed by wiki-builder using SQLite FTS5 BM25 retrieval. It delivers top passages with citations so the agent builds on existing notes. CX Codex +1 ★ 2,966repo stars orchestrator orchestrator — a subagent for Claude Code that splits complex builds into three phases: research, plan, implement. Each phase requires approval before the next — use it for features touching 5+ files or needing architecture decisions. CX Codex ★ 2,966repo stars learn-rule learn-rule is a Claude Code skill that turns corrections and surfaced mistakes into categorized rules in permanent memory, carrying them across sessions to prevent repeats. CX Codex +1 ★ 2,966repo stars cost-analyst cost-analyst reviews session token use, spots costly operations, and checks cache hits to suggest concrete ways to lower session costs. CX Codex ★ 2,966repo stars context-engineer context-engineer audits context window usage across project files, tools, and MCP servers. Useful when sessions run slow or hit token compaction too often. CX Codex ★ 2,966repo stars pre-flight-discipline The pre-flight-discipline rule makes Claude Code surface assumptions, limit edits to the request, and verify multi-step work. It fits projects where drive-by changes are a concern. CX Codex +1 ★ 2,966repo stars smart-commit smart-commit runs lint, typecheck and tests before a commit, scans staged code for leftovers, then writes a conventional commit message from the diff. CX Codex +1 ★ 2,966repo stars

Project sponsors

Companies that keep this analytics open