develop

Drives a feature from one-line description to squash-merged commit via worktree, review, and cleanup.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/forhas/pure-dev --skill develop-forhas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: develop
Source: https://github.com/forhas/pure-dev/tree/main/plugins/quick-dev/skills/develop
Command: npx skills add https://github.com/forhas/pure-dev --skill develop-forhas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a feature idea into merged code normally requires manually juggling branches, worktrees, PRs, review rounds, and cleanup. This Skill automates that entire end-to-end flow from a single feature description, leaving the repository on an up-to-date main branch with no leftover state. ## Core Features & Use Cases - End-to-end feature pipeline: preflight checks, isolated git worktree creation, flow triage (feature-dev or superpowers), build, verification, PR creation, review loop, squash-merge, and full cleanup. - Dual mode operation: GitHub mode with PR-based review (Codex or Copilot reviewer) or local mode with local review and squash-merge when GitHub tooling is unavailable. - Non-interactive automation: a --non-interactive flag self-answers every checkpoint so the flow runs unattended from description to merge. - Use Case: Run /quick-dev:develop add rate limiting to the API and the Skill creates a worktree, builds the feature via the chosen flow, opens a PR with frozen acceptance criteria, drives the review loop, squash-merges, and deletes the worktree and branch. ## Quick Start Ask the assistant to run /quick-dev:develop followed by a one-sentence description of the feature you want built and merged.

Frequently Asked Questions about develop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I develop a feature end to end with one command?

Run /quick-dev:develop followed by a feature description. The flow creates an isolated git worktree, builds the feature via feature-dev or superpowers, opens a PR, runs the review loop, squash-merges to main, and cleans up the worktree and branch.

What is the difference between feature-dev and superpowers flows?

The flow-triage step picks between them, or you can force one with --flow=feature-dev or --flow=superpowers. Feature-dev runs an explore-architect-implement cycle, while superpowers chains brainstorming, plan writing, plan review, and subagent-driven development.

Can I run the develop flow without GitHub?

Yes. If the gh CLI, authentication, repo reachability, or jq checks fail, the flow falls back to local mode. Local mode performs a local review and squash-merge directly onto the main branch without creating a pull request.

How do I run the develop skill non-interactively?

Pass the --non-interactive flag with your feature description. The flow then self-answers every checkpoint, including build-flow approval gates, and only stops on explicit failure conditions such as a blocked plan review.

Why does the develop flow stop after installing plugins?

Newly installed plugins are not loaded into the running session, so the flow stops once and asks you to run /reload-plugins and re-run the command. Continuing without a reload would fail when invoking the feature-dev or superpowers skills.

What happens if the plan review finds critical issues?

Under --auto, a PLAN-REVIEW: blocked result stops the run and leaves the worktree, branch, and plan intact for inspection. You can fix the plan in place and run subagent-driven development directly, or delete the worktree and re-run with a revised description.