agentmods.dev

feature-workflow

A workflow guide for planning and delivering software features in stages. It covers specifications, implementation phases, progress tracking, pull requests, and archiving.

In plain words
What is it for?
Use it when starting a feature or migration, writing a specification, splitting work into phases, managing pull requests, tracking progress, or archiving completed specs.
Why use it?
It provides a shared process for turning a feature idea into tracked implementation work and closing it out afterwards.

Skill for Claude CodeCodex

2 1mo ago A scan 53 tokens original MIT
View the source file arraydude/agent-skills
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/arraydude/agent-skills/feature-workflow
Any agent
npx skills add arraydude/agent-skills --skill feature-workflow
Clone the repo
git clone --depth 1 https://github.com/arraydude/agent-skills

Made for: Claude Code, Codex.

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 930 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00053 $0.00930
Opus 5 $0.00026 $0.00465
Sonnet 5 $0.00011 $0.00186
Haiku 4.5 $0.00005 $0.00093

Measured yesterday against content hash 7386df9b00ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feature-workflow scanned grade A with 0 findings 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 yesterday.

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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/feature-workflow/SKILL.md · 106 lines

How it starts

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

Feature Workflow

Comprehensive guide for planning, specifying, implementing, and archiving features. Contains 19 rules across 6 categories, derived from 18+ completed feature specs.

When to Apply

Reference these guidelines when:

  • Starting a new feature or migration
  • Creating or updating a spec document
  • Breaking work into implementation phases
  • Tracking progress within a spec
  • Deciding PR scope and branch strategy
  • Completing a feature and archiving the spec

Rule Categories by Priority

Priority Category Impact Prefix
1 Spec Structure & Content CRITICAL spec-
2 Phase Design CRITICAL phase-
3 Progress Tracking HIGH tracking-
4 PR Strategy HIGH pr-
5 Archival MEDIUM archive-
6 Workflow Collaboration MEDIUM workflow-

Quick Reference

1. Spec Structure & Content (CRITICAL)

  • spec-structure - Required spec document structure (title, metadata, ToC, sections)
  • spec-content-sections - What each section must contain (Executive Summary, Goals, Architecture, Plan, Testing, Criteria)
  • spec-current-state-analysis - Always start with current state: code inventory, problems with evidence
  • spec-living-document - Update spec throughout implementation, never delete history

2. Phase Design (CRITICAL)

  • phase-zero-foundation - Phase 0 is always foundation/infrastructure work
  • phase-decomposition - Break work into independently reviewable, shippable phases
  • phase-dependency-ordering - Order phases by dependency chain

3. Progress Tracking (HIGH)

  • tracking-status-indicators - Use consistent status indicators and progress trackers
  • tracking-completion-reports - Write completion reports per phase
  • tracking-metrics-tables - Include before/after metrics tables

4. PR Strategy (HIGH)

  • pr-target-develop-branch - CRITICAL: feature PRs always target develop, never main
  • pr-per-phase-strategy - One PR per phase for reviewability
  • pr-branch-naming - Branch naming follows GitFlow conventions
  • pr-scope-and-review - Keep PRs focused with clear scope documentation

Read the full file on GitHub · 106 lines

Files

What ships with it

20 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.

  1. yesterday First seen · 106 lines · 53 tokens per session scan A 7386df9b00ab

Subscribe to this mod's changes

feature-workflow is a skill published in the GitHub repository arraydude/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 930 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

PlanningProductivityWriting and docs
Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens