Agent skill

Feature Dev

by 6BNBN in 6BNBN/FlowPilot

A skill your agent uses when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.

MITAuto-check passedAgent Workflows

Install Feature Dev

skills CLI
$ npx skills add 6BNBN/FlowPilot --skill feature-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 6BNBN/FlowPilot feature-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/6BNBN/FlowPilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'兼容codex@cursor一键安装技能/codex一键安装技能/纯手动安装/skills/feature-dev' .claude/skills/feature-dev && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
feature-dev
GitHub stars
134
Token cost
~823 tokens
SKILL.md length
406 words
Files
5 (incl. references)
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.

  • Works in 7 steps: Discovery → Codebase Exploration → Clarifying Questions → …
  • The user asks to build a new feature and wants a structured Codex CLI workflow with discovery
  • SKILL.md covers Source of truth, Core Principles, Phase 1: Discovery and Phase 2: Codebase Exploration, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Feature Dev is an agent skill from 6BNBN/FlowPilot. Use when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/agent-prompts/code-architect.md`, `references/agent-prompts/code-explorer.md` and `references/agent-prompts/code-reviewer.md`).

It sits in Agent Workflows, covering Requirements gathering. The repository describes itself as: 一句需求,自动拆任务、并行多代理写码、断点恢复、验证收尾。FlowPilot 让 Claude Code / Codex / Cursor / snow-cli 进入真正的自动开发流程。 The licence is MIT.

When your agent uses it

  • The user asks to build a new feature and wants a structured Codex CLI workflow with discovery
  • Clarifying questions
  • Architecture comparison

Example prompts

  • “/feature-dev”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Discovery
  2. Codebase Exploration
  3. Clarifying Questions
  4. Architecture Design
  5. Implementation
  6. Quality Review
  7. Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 57b1d49. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feature Dev loads about 823 tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 48 tokens; SKILL.md has 406 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~823
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 6BNBN/FlowPilot at commit 57b1d49, republished under its MIT licence (© 6BNBN). 406 words, ~823 tokens.

Download SKILL.mdSave it as .claude/skills/feature-dev/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
feature-dev
description
Use when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.

Codex-Native Feature Development

Use this workflow when a feature request needs structured discovery before implementation. Keep update_plan current throughout, and use parallel explorer subagents for research only when their scopes are independent.

Source of truth

eferences/feature-dev-command.md

eferences/agent-prompts/code-architect.md

eferences/agent-prompts/code-explorer.md

eferences/agent-prompts/code-reviewer.md

Core Principles

  • Ask clarifying questions early when behavior, edge cases, or scope are underspecified.
  • Understand before acting by reading existing code patterns first.
  • Read the files surfaced by subagents instead of relying on summaries alone.
  • Prefer simple, maintainable designs over clever abstractions.
  • Use update_plan to track progress and checkpoints.

Phase 1: Discovery

Goal: Understand what needs to be built.

Actions:

  1. Create a plan that covers discovery, design, implementation, and review.
  2. If the request is underspecified, ask concrete clarifying questions.
  3. Summarize your understanding and confirm it with the user.

Phase 2: Codebase Exploration

Goal: Understand relevant code and patterns.

Actions:

  1. Spawn 2-3 explorer subagents in parallel with disjoint research scopes.
  2. Ask each subagent to return the 5-10 most important files to read next.
  3. Read the returned files yourself and consolidate the patterns you found.

Phase 3: Clarifying Questions

Goal: Resolve ambiguities before design.

Actions:

  1. Review the request and the exploration findings.
  2. Identify missing details around scope, data flow, UX, errors, compatibility, and testing.
  3. Present the open questions clearly.
  4. Wait for user answers before designing architecture.
Show full SKILL.md (183 more words)Show less

Phase 4: Architecture Design

Goal: Compare implementation approaches with trade-offs.

Actions:

  1. If the feature is large enough to justify it, spawn 2-3 explorer or worker subagents to propose different architectural approaches.
  2. Compare the approaches by change size, maintainability, risk, and implementation speed.
  3. Recommend one approach and explain why it fits best.
  4. Ask the user to confirm the direction.

Phase 5: Implementation

Goal: Build the chosen solution.

Actions:

  1. Do not start coding until the user approves the design.
  2. Re-read the relevant files before editing.
  3. Implement the approved approach with minimal, focused changes.
  4. Update update_plan as work progresses.

Phase 6: Quality Review

Goal: Catch bugs, unnecessary complexity, and convention drift.

Actions:

  1. Spawn review subagents with different lenses such as correctness, simplicity, and conventions.
  2. Consolidate the findings into a short actionable list.
  3. Present the findings and recommended fixes.
  4. Address the agreed changes before final handoff.

Phase 7: Summary

Goal: Hand off the finished work clearly.

Actions:

  1. Mark the plan complete.
  2. Summarize what was built, key decisions, files touched, and suggested next steps.

© 6BNBN, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in 兼容codex@cursor一键安装技能/codex一键安装技能/纯手动安装/skills/feature-dev of 6BNBN/FlowPilot.

  • SKILL.md
  • references/agent-prompts/code-architect.md
  • references/agent-prompts/code-explorer.md
  • references/agent-prompts/code-reviewer.md
  • references/feature-dev-command.md

Open the folder on GitHubat commit 57b1d49

Compare with similar skills

Feature Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Feature Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Feature Dev this skill6BNBN/FlowPilot134—~823Automated safety check: PassMIT
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills103k6 repos~3.8kAutomated safety check: PassMIT
Grillingpietheinstrengholt/rssmonster56432 repos~510Automated safety check: PassMIT
Agentic Workflow Designerdotnet/Open-XML-SDK4.6k2 repos~3.5kAutomated safety check: PassMIT
Ask User QuestionMemTensor/MemOS12k—~1kAutomated safety check: PassApache-2.0

Similar skills

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    103k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • Grilling

    pietheinstrengholt/rssmonster

    Grill the user relentlessly about a plan, decision, or idea.

    564 GitHub starsUsed in 32 repos~510 tokens
    Agent WorkflowsAuto-check passed
  • Agentic Workflow Designer

    dotnet/Open-XML-SDK

    Official

    Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.

    4.6k GitHub starsUsed in 2 repos~3.5k tokens
    Agent WorkflowsAuto-check passed
  • Ask User Question

    MemTensor/MemOS

    Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.

    12k GitHub stars~1k tokensUpdated 9 days ago
    Agent WorkflowsAuto-check passed
  • Brainstorming Before Building

    jnMetaCode/superpowers-zh

    Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.

    8.3k GitHub stars~1.8k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

More from 6BNBN/FlowPilot

All 21 skills in this repo
  • Playwright

    6BNBN/FlowPilot

    A skill your agent uses when the task requires automating a real browser from the terminal in Cursor, including navigation, form filling, snapshots, screenshots, data extraction, and UI-flow…

    134 GitHub stars~1k tokensUpdated 6 mo ago
    Auto-check passed
  • Code Review

    6BNBN/FlowPilot

    A skill your agent uses when the user asks to review a pull request or diff with a structured Codex CLI workflow using parallel review passes and filtered actionable findings.

    134 GitHub stars~624 tokensUpdated 6 mo ago
    Auto-check passed
  • A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.

    134 GitHub starsUsed in 1 repo~301 tokens
    Auto-check passed
  • Writing Skills

    6BNBN/FlowPilot

    A skill your agent uses when creating, editing, or validating Cursor custom skills, especially when deciding where they should live, how they should be named, and how to describe when they apply.

    134 GitHub stars~322 tokensUpdated 6 mo ago
    Auto-check passed
  • Code Review

    6BNBN/FlowPilot

    A skill your agent uses when the user asks for a code review of local files, a workspace, a branch diff, or a pull request.

    134 GitHub stars~465 tokensUpdated 6 mo ago
    Auto-check passed
  • Feature Dev

    6BNBN/FlowPilot

    A skill your agent uses when building a new feature or substantial behavior change in Cursor and the user wants a structured workflow from discovery through implementation and review.

    134 GitHub stars~439 tokensUpdated 6 mo ago
    Auto-check passed

Categories

Questions about Feature Dev

What does Feature Dev do?

A skill your agent uses when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review. Feature Dev is an agent skill from 6BNBN/FlowPilot. Use when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.

When should I use Feature Dev?

Feature Dev fits situations like: the user asks to build a new feature and wants a structured Codex CLI workflow with discovery; clarifying questions; architecture comparison.

How do I install Feature Dev in Claude Code?

Run `npx skills add 6BNBN/FlowPilot --skill feature-dev -a claude-code`. Or copy the skill folder (兼容codex@cursor一键安装技能/codex一键安装技能/纯手动安装/skills/feature-dev in 6BNBN/FlowPilot) into .claude/skills/feature-dev in your project. Claude Code loads it when a task matches its description.

How do I install Feature Dev in Codex?

Run `npx skills add 6BNBN/FlowPilot --skill feature-dev -a codex`. Or copy the skill folder (兼容codex@cursor一键安装技能/codex一键安装技能/纯手动安装/skills/feature-dev in 6BNBN/FlowPilot) into .agents/skills/feature-dev in your project. Codex loads it when a task matches its description.

Can I use Feature Dev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 6BNBN/FlowPilot --skill feature-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-dev, .gemini/skills/feature-dev, .github/skills/feature-dev and .opencode/skills/feature-dev in your project.

What does Feature Dev need to run?

SKILL.md names no scripts, command-line tools or credentials: Feature Dev is instructions for the agent only.

Does Feature Dev access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Feature Dev safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Feature Dev use?

Feature Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Feature Dev use?

About 823 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.

What are the alternatives to Feature Dev?

Skills that share tags, products or a category with Feature Dev: Using Superpowers (farm-fe/farm, 5.6k stars), Interview Me (addyosmani/agent-skills, 103k stars), Grilling (pietheinstrengholt/rssmonster, 564 stars) and Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Feature Dev?

6BNBN (a GitHub user) maintains it in 6BNBN/FlowPilot, which has 134 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on March 13, 2026.

Source: 6BNBN/FlowPilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.