What is feature-workflow?

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

Use it when starting a feature or migration, writing a specification, splitting work into phases, managing pull requests, tracking progress, or archiving completed specs.

It provides a shared process for turning a feature idea into tracked implementation work and closing it out afterwards.

feature-workflow — Skill for Claude Code and Codex by arraydude

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.

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.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/arraydude/agent-skills/feature-workflow/github.svg)](https://agentmods.dev/skills/arraydude/agent-skills/feature-workflow)

Your own site

<a href="https://agentmods.dev/skills/arraydude/agent-skills/feature-workflow"><img src="https://agentmods.dev/badge/skills/arraydude/agent-skills/feature-workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/arraydude/agent-skills/feature-workflow"><img src="https://agentmods.dev/badge/skills/arraydude/agent-skills/feature-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00053	$0.00930
Opus 5.5	$0.00021	$0.00372
Sonnet 5.5	$0.00011	$0.00186
Haiku 4.5	$0.00005	$0.00093

Measured 1mo ago against content hash 7386df9b00ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

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.

1mo ago 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 3mo ago), licensed MIT. It adds 53 tokens to every session and 930 once invoked, about $0.0002 per session on Opus 5.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.

Planning Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens