agentleFS
arraydudearraydude/agent-skills/skills/feature-workflow/SKILL.md

feature-workflow

Skill2 starsChanged 3 days agoMITView on GitHub

Feature planning, specification, phased implementation, progress tracking, per-phase PRs, and archival workflow. Use when starting a new feature, creating spec documents, breaking work into phases, tracking progress, managing PRs, or archiving completed specs.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Refinement: - Update spec based on feedback

    line 80
  2. Distinctive:

    Read individual rule files for detailed explanations and code examples:

    line 87

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

PriorityCategoryImpactPrefix
1Spec Structure & ContentCRITICALspec-
2Phase DesignCRITICALphase-
3Progress TrackingHIGHtracking-
4PR StrategyHIGHpr-
5ArchivalMEDIUMarchive-
6Workflow CollaborationMEDIUMworkflow-

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

5. Archival (MEDIUM)

  • archive-when-to-archive - Archive after all phases complete and PRs merged
  • archive-preservation-format - Preserve completion notes, learnings, and metrics

6. Workflow Collaboration (MEDIUM)

  • workflow-collaboration-loop - Iterative planning between AI and developer
  • workflow-spec-placement - Place specs under the relevant package .claude/ directory
  • workflow-iteration-patterns - How to iterate when requirements change

Core Workflow

  1. Discovery - Developer describes the feature/problem
  2. Analysis - Explore codebase, document current state
  3. Proposal - Draft spec with architecture and phases
  4. Review - Developer reviews, provides feedback
  5. Refinement - Update spec based on feedback
  6. Approval - Developer confirms plan
  7. Implementation - Phase-by-phase with per-phase PRs
  8. Archive - Move completed spec, capture learnings

How to Use

Read individual rule files for detailed explanations and code examples:

rules/spec-structure.md
rules/phase-decomposition.md
rules/tracking-status-indicators.md
rules/pr-per-phase-strategy.md
rules/archive-when-to-archive.md
rules/workflow-collaboration-loop.md

Each rule file contains:

  • Brief explanation of why it matters
  • Incorrect example (anti-pattern)
  • Correct example (best practice)

Full Compiled Document

For the complete guide with all rules expanded: AGENTS.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.