| name | sc-implement |
| description | Feature implementation with intelligent persona activation, task orchestration, and MCP integration. Use when implementing features, APIs, components, services, or coordinating multi-agent development. Triggers on requests for code implementation, feature development, or complex task orchestration. |
Implementation Skill
Comprehensive feature implementation with coordinated expertise and systematic development.
Quick Start
/sc:implement [feature-description] --type component|api|service|feature
/sc:implement dashboard widget --framework react|vue|express
/sc:implement [task] --orchestrate --strategy systematic|agile|enterprise
Behavioral Flow
- Analyze - Examine requirements, detect technology context
- Plan - Choose approach, activate relevant personas
- Generate - Create implementation with framework best practices
- Validate - Apply security and quality validation
- Integrate - Update docs, provide testing recommendations
Flags
| Flag | Type | Default | Description |
|---|
--type | string | feature | component, api, service, feature |
--framework | string | auto | react, vue, express, etc. |
--safe | bool | false | Enable safety constraints |
--with-tests | bool | false | Generate tests alongside code |
--fast-codex | bool | false | Streamlined path, skip multi-persona |
--orchestrate | bool | false | Enable hierarchical task breakdown |
--strategy | string | systematic | systematic, agile, enterprise, parallel, adaptive |
--delegate | bool | false | Enable intelligent delegation |
Personas Activated
- architect - System design, architectural decisions
- frontend - UI/component implementation
- backend - API/service implementation
- security - Security validation, auth concerns
- qa-specialist - Testing, quality assurance
- devops - Infrastructure, deployment
- project-manager - Task coordination (with --orchestrate)
MCP Integration
- PAL MCP - Consensus for architectural/security decisions
- Rube MCP - External automation (ticketing, CI hooks)
Guardrails
- Start in analysis mode; produce scoped plan before touching files
- Only mark complete when referencing concrete repo changes (filenames + diff hunks)
- Return plan + next actions if tooling unavailable
- Prefer minimal viable change; skip speculative scaffolding
- Escalate to security persona before modifying auth/secrets/permissions
Evidence Requirements
This skill requires evidence. You MUST:
- Show actual file diffs or code changes
- Reference test results or lint output
- Never claim code exists without proof
Examples
React Component
/sc:implement user profile component --type component --framework react
API with Tests
/sc:implement user auth API --type api --safe --with-tests
Complex Orchestration
/sc:implement "enterprise auth system" --orchestrate --strategy systematic --delegate
Resources
