arraydude 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 evidencespec-living-document- Update spec throughout implementation, never delete history
2. Phase Design (CRITICAL)
phase-zero-foundation- Phase 0 is always foundation/infrastructure workphase-decomposition- Break work into independently reviewable, shippable phasesphase-dependency-ordering- Order phases by dependency chain
3. Progress Tracking (HIGH)
tracking-status-indicators- Use consistent status indicators and progress trackerstracking-completion-reports- Write completion reports per phasetracking-metrics-tables- Include before/after metrics tables
4. PR Strategy (HIGH)
pr-target-develop-branch- CRITICAL: feature PRs always targetdevelop, nevermainpr-per-phase-strategy- One PR per phase for reviewabilitypr-branch-naming- Branch naming follows GitFlow conventionspr-scope-and-review- Keep PRs focused with clear scope documentation
5. Archival (MEDIUM)
archive-when-to-archive- Archive after all phases complete and PRs mergedarchive-preservation-format- Preserve completion notes, learnings, and metrics
6. Workflow Collaboration (MEDIUM)
workflow-collaboration-loop- Iterative planning between AI and developerworkflow-spec-placement- Place specs under the relevant package .claude/ directoryworkflow-iteration-patterns- How to iterate when requirements change
Core Workflow
- Discovery - Developer describes the feature/problem
- Analysis - Explore codebase, document current state
- Proposal - Draft spec with architecture and phases
- Review - Developer reviews, provides feedback
- Refinement - Update spec based on feedback
- Approval - Developer confirms plan
- Implementation - Phase-by-phase with per-phase PRs
- 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