skills.rest
fx
fxCOMMUNITY
Explore all skills by this author →
GitHub

dev

Orchestrates the full SDLC lifecycle from requirements through implementation, review, CI, and merge.

Updated Nov 2, 2025
Search Tags:#code review#pull request#github#workflow orchestration#sdlc#ci#sub-agent delegation
One-click install
npx skills add https://github.com/fx/skills --skill dev-fx
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: dev
Source: https://github.com/fx/skills/tree/main/skills/dev
Command: npx skills add https://github.com/fx/skills --skill dev-fx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating a complete software change — requirements analysis, planning, implementation, code review, CI remediation, and merge — requires many judgment calls and handoffs that are easy to get wrong or skip. This Skill enforces a mandatory, ordered lifecycle so every explicitly invoked change passes through the same gates with delegated sub-agents, scope discipline, and converged review before merging. ## Core Features & Use Cases - End-to-end SDLC orchestration: Runs ordered steps from GitHub authentication and branch creation through requirements analysis, planning, implementation, pre-PR review, PR preparation, CI monitoring, and finalization. - Mandatory sub-agent delegation: Requirements, planning, and implementation are delegated to sub-agents that load the requirements-analyzer, planner, and coder skills, with tier-based model sizing for each role. - Scope Brief and finding ledger: Freezes the user's verbatim request into a Scope Brief carried through every delegate and reviewer, and tracks findings with classification, materiality tiers, and convergence rules. - Review and CI integration: Drives Codex local review plus Copilot and CodeRabbit PR-level reviews, batches findings into single fix passes, and enforces head-discipline rules so evidence stays SHA-scoped. - Use Case: A user invokes /dev on a GitHub issue; the Skill analyzes requirements, plans, implements via delegates, runs local and hosted review until convergence, verifies the test plan, and hands off a merge-ready PR. ## Quick Start Invoke the dev lifecycle by asking the agent to run /dev on a specific task or GitHub issue, and it will execute the full workflow from branch creation through a reviewed, CI-green pull request.

Frequently Asked Questions about dev

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

FAQPage Schema
How do I run a full development lifecycle on a GitHub issue?â–¼

Explicitly invoke the dev lifecycle with the task or issue number. The workflow fetches the issue, analyzes requirements, plans, implements via delegated sub-agents, runs Codex and hosted reviews, and produces a merge-ready pull request.

How does the dev skill delegate implementation work?â–¼

It spawns general-purpose sub-agents that load the requirements-analyzer, planner, and coder skills from their prompts, each assigned a large, medium, or small model tier based on task shape. The coordinator never writes implementation code itself.

Which code reviewers does the dev lifecycle run?â–¼

Codex runs locally before the PR via the codex-review skill, and Copilot plus CodeRabbit run at the PR level where configured. Findings are triaged against the Scope Brief, classified, and batched into single fix passes until review converges.

Does the dev skill work on hosts other than Claude Code?â–¼

Yes, the host-adapters reference maps its seven orchestration operations onto Claude Code and Codex, including delegation, waiting, messaging, and long-running waits. Other hosts can be added by mapping the same operations.

When should I not use the dev lifecycle?â–¼

Do not use it for ordinary coding requests that were not explicitly invoked as /dev, or for incidental operations like status checks and branch syncs. It is an explicit-use workflow, not an automatic response to any coding task.

What happens if review does not converge?â–¼

Each review channel caps at 15 iterations counting the initial pass. Reaching the bound is treated as a failure to converge: the workflow stops, reports the per-pass trend and unresolved findings, and escalates to the user rather than merging.

Related Skills

Explore More Software Engineering Skills→
biz-Streambiz-Stream

start-task

Create a GitHub issue and matching branch for development tasks.

Official
Intermediate
sarkarshivaditya-labsarkarshivaditya-lab

ci-monitoring

Monitors GitHub PR CI checks, resolves failures and review feedback, then merges.

Community
Advanced
narusenianarusenia

pr-review

Review GitHub pull requests in isolated worktrees against project specifications.

Community
Advanced
droppiidroppii

ck:fix

Orchestrate end-to-end bug fixes across debugging, planning, implementation, testing, and review.

Official
Advanced