agentleFS
4444J994444J99/a-i--skills/skills/development/feature-workflow-orchestrator/SKILL.md

feature-workflow-orchestrator

Skill17 starsChanged 5 months agoApache-2.0Archived repositoryView on GitHub

End-to-end feature development orchestration from planning through deployment with quality gates

  • Commits and pushes

1 other project uses a version of this.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Document as you go

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Orchestrator

Complete workflow for feature development from concept to production.

Feature Development Lifecycle

┌──────────────────────────────────────────────────┐
│                                                  │
│  PLAN → DESIGN → IMPLEMENT → TEST → REVIEW      │
│    ↓       ↓         ↓         ↓       ↓        │
│  Scope  Arch     Code+Tests  QA    PR+Deploy    │
│                                                  │
└──────────────────────────────────────────────────┘

Phase 1: Planning

Feature Specification

# Feature: [Name]

## Problem Statement
What problem does this solve?

## User Stories
- As a [role], I want to [action], so that [benefit]

## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2

## Technical Considerations
- Dependencies
- Performance requirements
- Security concerns

## Success Metrics
- Metric 1: Target value
- Metric 2: Target value

Phase 2: Design

Architecture Decision

## Architecture Decision: [Title]

**Context**: What necessitates this decision
**Options**:
1. Option A - Pros/Cons
2. Option B - Pros/Cons

**Decision**: Chosen approach
**Consequences**: Impact on codebase

Phase 3: Implementation

TDD Cycle

  1. Write failing tests
  2. Implement minimal code
  3. Refactor while green
  4. Document as you go

Branch Strategy

# Create feature branch
git checkout -b feature/user-authentication

# Regular commits
git commit -m "feat(auth): add login endpoint"
git commit -m "test(auth): add login tests"
git commit -m "docs(auth): update API docs"

Phase 4: Testing

Quality Gates

  • All tests pass (80%+ coverage)
  • No type errors
  • No lint warnings
  • Security scan clean
  • Performance benchmarks met

Verification

# Run verification loop
npm run build
npm run type-check
npm run lint
npm test -- --coverage
npm run security-scan

Phase 5: Review & Deploy

Pull Request Checklist

  • Description explains what and why
  • Tests included
  • Documentation updated
  • Breaking changes noted
  • Screenshots/demo for UI changes

Deployment

# Merge to main after approval
git checkout main
git merge --no-ff feature/user-authentication

# Tag release
git tag -a v1.2.0 -m "Release v1.2.0: Add user authentication"
git push origin v1.2.0

Integration Points

Complements:

  • tdd-workflow: For test-first development
  • verification-loop: For quality gates
  • project-orchestration: For project management
  • deployment-cicd: For automated deployment

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.