Develop Team
This skill should be used when the user asks to "develop a feature", "implement a ticket", "build PROJ-123", "run the development pipeline", "develop this ticket end to end", or wants fully autonomous feature implementation with parallel research agents, planning, phased implementation, review, and PR creation. Zero checkpoints; pauses only on blockers.
Install
npx skills add EricTechPro/startup-claude-skills --skill develop-teamgit clone --depth 1 https://github.com/EricTechPro/startup-claude-skills.git /tmp/startup-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/startup-claude-skills/skills/develop-team ~/.claude/skills/develop-teamPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Develop Team Orchestrate a full feature development cycle using parallel sub-agents. Takes a ticket reference or freeform task and drives it through deep research, planning (with design/test/migration specs), implementation with per-phase test generation, review, and automatic PR creation — fully autonomous with no checkpoints unless a genuine blocker is detected. ## When to Use This Skill - **Starting a new feature** - Hand off a ticket and let the pipeline research, plan, and implement - **Exploring before implementing** - Use `plan-only=true` to get a researched plan without writing code - **Structured development** - Parallel research + review instead of ad-hoc implementation ## Parameters | Parameter | Default | Description | |-----------|---------|-------------| | `type` | `auto` | Feature type: `auto\|ui-heavy\|full-stack\|backend-only\|async-heavy` | | `auto-commit` | `true` | Create atomic commits after each implementation phase | | `skip-review` | `false` | Skip refactor and review phases | | `skip-tests` | `false` | Skip per-phase test generation | | `skip-pr` | `false` | Skip automatic PR creation | | `skip-migrations` | `false` | Skip DB migration analysis and application | | `plan-only` | `false` | Stop after planning (no implementation) | ## Invocation
Details
- Skill name
develop-team- Repository
- EricTechPro/startup-claude-skills
- Path
skills/develop-team/SKILL.md- License
- MIT
- Repo updated
- 5 June 2026
FAQ
What does the Develop Team skill do?
This skill should be used when the user asks to "develop a feature", "implement a ticket", "build PROJ-123", "run the development pipeline", "develop this ticket end to end", or wants fully autonomous feature implementation with parallel research agents, planning, phased implementation, review, and PR creation. Zero checkpoints; pauses only on blockers.
How do I install the Develop Team skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add EricTechPro/startup-claude-skills --skill develop-team. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Develop Team popular?
It lives in EricTechPro/startup-claude-skills, which has 58 GitHub stars and 18 forks.
Related skills
Fix Sentry
58EricTechPro/startup-claude-skills
Scan all unresolved Sentry errors, group by root cause, fix in batch with TDD, and resolve in Sentry after deploy. Use when the user says 'fix sentry errors', 'scan sentry', 'resolve sentry issues', 'fix all errors', 'sentry cleanup', or wants to proactively fix production errors from Sentry monitoring.
Fix Ticket
58EricTechPro/startup-claude-skills
Automate the full Jira bug-fix pipeline end-to-end. Use when the user says 'fix ticket', 'fix PROJ-123', 'fix this bug', 'resolve PROJ-XXX', 'fix and ship this ticket', or passes a Jira ticket ID for autonomous bug resolution. Reads the Jira ticket, implements the fix, reviews it, commits, moves the ticket to QA, assigns to QA engineer, and comments with a summary. Also use when the user wants to automate the fix-review-commit-handoff cycle for any Jira bug ticket.
Playwright QA CLI
58EricTechPro/startup-claude-skills
Automated QA testing using playwright-cli (CLI tool, NOT MCP tools). Provisions a test user, opens a headless browser, logs in, navigates to target pages, takes screenshots, and generates a REPORT.md. Two modes: VERIFY (reproduce a bug before fixing) and CHECK (confirm a fix works). Use this skill whenever the user says 'QA this', 'test this fix', 'verify this bug', 'smoke test', 'check if this works', 'reproduce this issue', 'run playwright QA', or 'playwright-qa-cli'. Also triggered from /fix-ticket at pre-fix and post-fix stages. Works for any page or user flow — not limited to specific fea
Gitchamber
43remorses/gitchamber
CLI to download npm packages, PyPI packages, crates, or GitHub repo source code into node_modules/.gitchamber/ for analysis. Use when you need to read a package's inner workings, documentation, examples, or source code. Alternative to opensrc that stores in node_modules/ for zero-config gitignore/vitest/tsc compatibility. After fetching, analyze files with grep, read, and other tools.
Tikhub API Helper
44liangdabiao/social_research_agent
Search and query TikHub APIs for TikTok, Douyin, Xiaohongshu, Lemon8, Instagram, YouTube, Twitter, Reddit, and more. Use when user asks about needs to fetch data from social media platforms. Supports both English and Chinese queries.
Developer Growth Analysis
52ArogyaReddy/ComposioHQ-awesome-claude-skills
Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.