feature-workflow-orchestrator

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

5 stars

Best use case

feature-workflow-orchestrator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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

Teams using feature-workflow-orchestrator should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/feature-workflow-orchestrator/SKILL.md --create-dirs "https://raw.githubusercontent.com/organvm-iv-taxis/a-i--skills/main/distributions/claude/skills/feature-workflow-orchestrator/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/feature-workflow-orchestrator/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How feature-workflow-orchestrator Compares

Feature / Agent	feature-workflow-orchestrator	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

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

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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

```markdown
# 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

```markdown
## 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

```bash
# 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

```bash
# 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

```bash
# 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

Related Skills

pentaphase-orchestrator

from organvm-iv-taxis/a-i--skills

Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.

tdd-workflow

from organvm-iv-taxis/a-i--skills

Test-driven development workflow with comprehensive coverage requirements including unit, integration, and E2E tests

research-synthesis-workflow

from organvm-iv-taxis/a-i--skills

Systematic methodology for gathering, analyzing, and synthesizing research from multiple sources into coherent insights and actionable knowledge.

project-alchemy-orchestrator

from organvm-iv-taxis/a-i--skills

A strategic guide for managing complex creative portfolios as a system of "organs" (Art, Commerce, Tools), diagnosing lifecycle stages (Nigredo, Albedo, Rubedo), and balancing the "Four Fields" of creative labor.

mcp-server-orchestrator

from organvm-iv-taxis/a-i--skills

Configure, deploy, and troubleshoot Model Context Protocol (MCP) servers for AI agent workflows. Use when setting up MCP servers, debugging connection issues, managing multi-server configurations, integrating with Claude Desktop/Code/Cowork, or designing custom tool servers. Triggers on MCP configuration, tool server development, Claude integration issues, or agent infrastructure setup.

agent-swarm-orchestrator

from organvm-iv-taxis/a-i--skills

Designs multi-agent systems with coordinated agent swarms, task distribution, inter-agent communication, and emergent collective behavior.

taxonomy-modeling-design

from organvm-iv-taxis/a-i--skills

Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.

systemic-ingestion-normalization

from organvm-iv-taxis/a-i--skills

Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.

system-environment-configuration

from organvm-iv-taxis/a-i--skills

Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.

landscape-discovery-audit

from organvm-iv-taxis/a-i--skills

Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.

governance-evolution-protocol

from organvm-iv-taxis/a-i--skills

Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.

dimension-surfacing

from organvm-iv-taxis/a-i--skills

Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.