A starting point for non-trivial development work that directs a feature through the appropriate development workflow.

Use it when starting, building, or implementing a feature and when you need the next development step selected.

It helps decide whether a task is a small edit, a standard feature, or a larger project before work begins.

start — Skill by uta2000

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/uta2000/feature-flow/start

Any agent

npx skills add uta2000/feature-flow --skill start

Clone the repo

git clone --depth 1 https://github.com/uta2000/feature-flow

Made for: Claude Code, Codex.

Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 29,066 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00086	$0.29066
Opus 5	$0.00043	$0.14533
Sonnet 5	$0.00017	$0.05813
Haiku 4.5	$0.00009	$0.02907

Measured 2d ago against content hash 09bb75065919, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

start scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

**Why:** The `Skill` tool has no `model` parameter — it inherits the parent model. The `Task` tool has an explicit `model` parameter. In YOLO mode there is no user interaction, so running skills inside a Task subagent wo

skills/start/SKILL.md · 1,455 lines

How it starts

The opening of the file, as written. The whole thing — 1,455 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Start — Lifecycle Orchestrator

Guide development work through the correct lifecycle steps, invoking the right skill at each stage. This is the single entry point for any non-trivial work.

Announce at start: "Starting the feature lifecycle. Analyzing your project to recommend the right tool..."

Triage

Before brainstorming, analyze your project description to determine the correct path: quick (bounded trivial edit confirmed by code), feature-flow (standard lifecycle), or GSD (multi-feature project).

Step 1: Check if tool selection is enabled

Read .feature-flow.yml and look for tool_selector.enabled:

If enabled: false → skip tool selection, proceed directly to brainstorming
If enabled: true or missing → continue to step 2

Step 2: Check for command-line overrides

Did the user include --feature-flow, --gsd, or --no-quick flag?

If --feature-flow present → remove flag from description, skip detection, use feature-flow
If --gsd present → remove flag from description, skip detection, launch GSD
If --no-quick present → remove flag from description, record no_quick_override = true, continue to step 3 (Quick-Path Confirmation will be skipped; heuristic scoring runs normally)
If --quick or any other --foo token is present that is NOT in --feature-flow / --gsd / --no-quick → surface: "Unknown flag --foo. Quick path is opt-out only (--no-quick); there is no --quick flag. Continuing with auto-detection." Strip the token from description and continue to step 3.
If no flags → continue to step 3

Step 3: Quick-Path Confirmation

Quick path is available when tool_selector.quick_path.enabled is true (default) and no_quick_override is not set (see Step 2 — set by the --no-quick flag). If either condition is false, skip this step entirely and continue to Step 4.

Run gates in strict order 0 → 4. First failure short-circuits immediately — do not run later gates. Pass budget: ≤5 Bash/Grep/Read/Glob tool calls total across all gates. In-process AST tokenization and byte-range overlap checks are free (do not count). If you reach 5 tool calls before all gates pass, abort confirmation and fall through silently.

Read the full file on GitHub · 1,455 lines

Files

What ships with it

12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 1,455 lines · 86 tokens per session scan B 09bb75065919

Subscribe to this mod's changes

start is a skill published in the GitHub repository uta2000/feature-flow (4 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 29,066 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Productivity

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

start