mcpField
F
feature-workflow

feature-workflow

github.com/arraydudeDevelopment2133 installsUpdated 16w ago
Repository

About feature-workflow

A feature development workflow guide for developers and AI agents, covering specification writing, phase planning, progress tracking, PR strategy, and archiving. Its 19 rules support collaboration from initial analysis through completion.

Key features

  1. 01Define specification structure and content
  2. 02Break implementation into phases
  3. 03Track phase progress and completion
  4. 04Set PR scope and branch strategy
  5. 05Archive specifications and learnings

Use cases

  1. 01Write a specification for a feature or migration
  2. 02Break a development plan into reviewable phases
  3. 03Track implementation progress by phase
  4. 04Archive specifications and learnings after merge

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/arraydude/agent-skills --skill feature-workflow

After installing, type/feature-workflowin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

AGENTS.md
rules/
archive-preservation-format.md
archive-when-to-archive.md
phase-decomposition.md
phase-dependency-ordering.md
phase-zero-foundation.md
pr-branch-naming.md
pr-per-phase-strategy.md
pr-scope-and-review.md
pr-target-develop-branch.md
spec-content-sections.md
spec-current-state-analysis.md
spec-living-document.md
spec-structure.md
tracking-completion-reports.md
tracking-metrics-tables.md
tracking-status-indicators.md
workflow-collaboration-loop.md
workflow-iteration-patterns.md
workflow-spec-placement.md

Details

From the project README

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

Comments

Markdown supported