skyfom-feature-complete
npx machina-cli add skill SkyfomLabs/skyfom-claude-orchestration/skyfom-feature-complete --openclawSkyfom Feature-Complete Developer
Composite skill that delivers production-ready features with parallel development, testing, and review.
Role
- Deliver production-ready features
- Ensure comprehensive test coverage
- Enforce quality gates
- Generate documentation
- Coordinate design, development, QA, and code review
Composition
This skill spawns 5 sub-skills in hybrid execution mode (3 parallel groups):
Group 1: Core Development + Design (Parallel)
- Backend Developer (Required)
- Frontend Developer (Required)
- Designer (Optional) - Creates design specs in parallel
Group 2: Quality Assurance (Parallel, after Group 1)
- QA Engineer (Required) - Creates test suite
- Code Reviewer (Required) - Reviews code quality
Execution Flow
Group 1 (Parallel):
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ Backend Dev │ │ Frontend Dev │ │ Designer │
│ │ │ │ │ (Optional) │
└──────┬───────┘ └──────┬───────┘ └──────────────┘
│ │
│ Outputs │
└────────┬────────┘
│
Group 2 (Parallel): ▼
┌──────────────────────┐
│ QA + Code Reviewer │
│ (Both in parallel) │
└──────────────────────┘
How to Use This Skill
This composite skill automatically:
- Spawns backend + frontend developers + designer in parallel
- Waits for development to complete
- Spawns QA + code reviewer in parallel to validate
- Aggregates all results
- Creates PR with complete feature + tests + docs
Workflow
Step 1: Analyze Requirements
Parse task to determine:
- Backend requirements
- Frontend requirements
- Design needs (optional)
- Testing requirements
- Quality standards
Step 2: Group 1 - Development (Parallel)
Spawn 3 agents IN PARALLEL (single message, 3 Task calls):
- Backend developer → Implements API/business logic
- Frontend developer → Implements UI components
- Designer → Creates design specs (if needed)
Step 3: Collect Development Outputs
From Group 1:
- Backend: API implementation, database changes
- Frontend: Components, pages, routing
- Designer: Design specs, Tailwind tokens
Step 4: Group 2 - Quality (Parallel)
Spawn 2 agents IN PARALLEL (single message, 2 Task calls):
- QA engineer → Creates tests (unit, integration, E2E)
- Code reviewer → Reviews code quality, security
Step 5: Quality Gate
Code reviewer must approve:
- ✅ No P0/P1 security issues
- ✅ No logic bugs
- ✅ Performance acceptable
- ✅ Code quality meets standards
QA must confirm:
- ✅ Test coverage > 80%
- ✅ All E2E tests pass
- ✅ No regressions
Step 6: Create PR
Create single PR containing:
- Backend implementation
- Frontend implementation
- Test suite (unit + integration + E2E)
- Design documentation (if applicable)
- Code review approval
Parallel Execution Example
// This skill uses the parallel execution framework
// Group 1: Development (3 agents in parallel)
const group1Tasks = [
{
subagent_type: 'general-purpose',
description: 'Backend implementation',
prompt: 'You are skyfom-backend-developer. Implement the backend...'
},
{
subagent_type: 'general-purpose',
description: 'Frontend implementation',
prompt: 'You are skyfom-frontend-developer. Implement the UI...'
},
{
subagent_type: 'general-purpose',
description: 'Design specifications',
prompt: 'You are skyfom-designer. Create design specs...'
}
];
// Spawn all 3 in single message with 3 Task calls
// Wait for completion...
// Group 2: Quality (2 agents in parallel)
const group2Tasks = [
{
subagent_type: 'general-purpose',
description: 'QA testing',
prompt: 'You are skyfom-qa. Create comprehensive tests...'
},
{
subagent_type: 'general-purpose',
description: 'Code review',
prompt: 'You are skyfom-code-reviewer. Review the code...'
}
];
// Spawn both in single message with 2 Task calls
Token Management
Estimated token usage:
- Backend: ~50k tokens
- Frontend: ~45k tokens
- QA: ~40k tokens
- Code Reviewer: ~30k tokens
- Designer: ~25k tokens (optional)
- Total: ~190k tokens (within limits)
Success Metrics
- All required sub-skills complete successfully
- Test coverage > 80%
- Zero P0/P1 code review issues
- All CI/CD checks pass
- PR approved and merged
- Design specs match implementation (if designer included)
Configuration
Edit composition.json to customize:
- Make designer required or optional
- Adjust token estimates
- Change error handling strategy
- Modify max parallel agents
Beads Commands
# Claim feature task
bd update <task-id> --status in_progress
# After all sub-skills complete
bd close <task-id> --reason "Feature complete with tests & review (PR #<number>)"
Integration
- Triggered by: PM assigns feature task
- Uses: Backend, Frontend, QA, Code Reviewer, Designer skills
- Reports to: PM with production-ready feature
- Output: Single PR with implementation + tests + docs
Quick Reference
# View composition
cat .claude/skills/skyfom-feature-complete/composition.json | jq
# Check execution groups
# Group 1: Backend, Frontend, Designer (parallel)
# Group 2: QA, Code Reviewer (parallel, after Group 1)
Source
git clone https://github.com/SkyfomLabs/skyfom-claude-orchestration/blob/main/skills/skyfom-feature-complete/SKILL.mdView on GitHub Overview
Skyfom Feature-Complete is a composite skill that orchestrates backend development, frontend work, and design in parallel, followed by QA and code review to deliver production-ready features. It ensures comprehensive test coverage, documentation, and quality gates as part of the feature delivery workflow. This approach reduces cycle time while maintaining high quality.
How This Skill Works
The skill spawns Group 1 in parallel (Backend Developer, Frontend Developer, and an optional Designer). After development completes, it spawns Group 2 in parallel (QA Engineer and Code Reviewer) to validate quality. It then aggregates all results and creates a single PR containing the backend, frontend, tests, and design documentation.
When to Use It
- When delivering a new feature that requires backend, frontend, and design inputs
- When you need rigorous testing, documentation, and enforced quality gates
- When optimizing delivery time by parallelizing work streams
- When coordinating cross-functional teams with a single, consolidated PR
- When implementing features with strict security and performance standards
Quick Start
- Step 1: Analyze requirements and identify backend, frontend, and design needs (design optional)
- Step 2: Spawn Group 1 tasks (Backend, Frontend, Designer) in parallel and wait for outputs
- Step 3: Spawn Group 2 tasks (QA, Code Reviewer) in parallel, enforce quality gates, then create a single PR
Best Practices
- Define requirements upfront for backend, frontend, design, testing, and quality standards
- Treat design as optional but plan for it within Group 1 to avoid bottlenecks
- Enforce automated tests and require test coverage > 80% for QA gates
- Require Code Reviewer approval before QA gates and PR creation
- Document the feature thoroughly and include all artifacts in the single PR
Example Use Cases
- Launch a new user onboarding flow with API, UI components, tests, and design docs
- Integrate a payments module end-to-end with tests and security reviews
- Roll out a feature flag with accompanying design specs and documentation
- Implement admin dashboard enhancements with design tokens and QA coverage
- Migrate a legacy endpoint, validating with tests, docs, and code review