Feature Workflow Orchestrator
Productivityfeature-workflow-orchestratorFeature Workflow Orchestrator is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
End-to-end feature development orchestration from planning through deployment with quality gates
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/feature-workflow-orchestrator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/feature-workflow-orchestrator, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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
- Write failing tests
- Implement minimal code
- Refactor while green
- 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