implement

Original：🇺🇸 English
Not Translated
1 scripts

Full-power feature implementation with parallel subagents. Use when implementing, building, or creating features.

1installs
Sourceyonatangross/skillforge-claude-plugin
Added on

NPX Install

npx skill4agent add yonatangross/skillforge-claude-plugin implement

SKILL.md Content

Implement Feature

Parallel subagent execution for feature implementation with scope control and reflection.

Quick Start

bash
/implement user authentication
/implement real-time notifications
/implement dashboard analytics

Step 0: Project Context Discovery

BEFORE any work, detect the project tier. This becomes the complexity ceiling for all patterns.

Auto-Detection

Scan codebase for signals: README keywords (take-home, interview), 
.github/workflows/
, Dockerfile, terraform/, k8s/, CONTRIBUTING.md.

Tier Classification

SignalTierArchitecture Ceiling
README says "take-home", time limit1. Interview (details)Flat files, 8-15 files
< 10 files, no CI2. HackathonSingle file if possible
.github/workflows/
, managed DB		3. MVPMVC monolith
Module boundaries, Redis, queues4. GrowthModular monolith, DI
K8s/Terraform, monorepo5. EnterpriseHexagonal/DDD
CONTRIBUTING.md, LICENSE6. Open SourceMinimal API, exhaustive tests
If confidence is low, use 
AskUserQuestion
to ask the user. Pass detected tier to ALL downstream agents — see 
scope-appropriate-architecture
.

Tier → Workflow Mapping

TierPhasesMax Agents
1. Interview1, 5 only2
2. Hackathon5 only1
3. MVP1-6, 93-4
4-5. Growth/EnterpriseAll 105-8
6. Open Source1-7, 9-103-4
Use 
AskUserQuestion
to verify scope (full-stack / backend-only / frontend-only / prototype) and constraints.

Orchestration Mode

  • Agent Teams (mesh) when 
    CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
    and complexity >= 2.5
  • Task tool (star) otherwise; 
    ORCHESTKIT_FORCE_TASK_TOOL=1
    to override
  • See Orchestration Modes

Task Management (MANDATORY)

Create tasks with 
TaskCreate
BEFORE doing any work. Each phase gets a subtask. Update status with 
TaskUpdate
as you progress.

Workflow (10 Phases)

PhaseActivitiesAgents
1. DiscoveryResearch best practices, Context7 docs, break into tasks—
2. Micro-PlanningDetailed plan per task (guide)—
3. WorktreeIsolate in git worktree for 5+ file features (workflow)—
4. Architecture5 parallel background agentsworkflow-architect, backend-system-architect, frontend-ui-developer, llm-integrator, ux-researcher
5. Implementation + TestsParallel agents, single-pass artifacts with mandatory testsbackend-system-architect, frontend-ui-developer, llm-integrator, test-generator, rapid-ui-designer
6. Integration VerificationCode review + real-service integration testsbackend, frontend, code-quality-reviewer, security-auditor
7. Scope CreepCompare planned vs actual (detection)workflow-architect
8. E2E VerificationBrowser + API E2E testing (guide)—
9. DocumentationSave decisions to memory graph—
10. ReflectionLessons learned, estimation accuracyworkflow-architect
See Agent Phases for detailed agent prompts and spawn templates.
For Agent Teams mode, see Agent Teams Phases.

Issue Tracking

If working on a GitHub issue, run the Start Work ceremony from 
issue-progress-tracking
and post progress comments after major phases.

Feedback Loop

Maintain checkpoints after each task. See Feedback Loop for triggers and actions.

Test Requirements Matrix

Phase 5 test-generator MUST produce tests matching the change type:
Change TypeRequired Tests
testing-patterns
Rules
API endpointUnit + Integration + Contract
integration-api
, 
verification-contract
, 
mocking-msw
DB schema/migrationMigration + Integration
integration-database
, 
data-seeding-cleanup
UI componentUnit + Snapshot + A11y
unit-aaa-pattern
, 
integration-component
, 
a11y-jest-axe
, 
e2e-playwright
Business logicUnit + Property-based
unit-aaa-pattern
, 
pytest-markers
, 
verification-property
LLM/AI featureUnit + Eval
llm-deepeval
, 
llm-mocking
, 
llm-structured
Full-stack featureAll of the aboveAll matching rules

Real-Service Detection (Phase 6)

Before running integration tests, detect infrastructure:
python
# Auto-detect real service testing capability (PARALLEL)
Glob(pattern="**/docker-compose*.yml")
Glob(pattern="**/testcontainers*")
Grep(pattern="testcontainers|docker-compose", glob="requirements*.txt")
Grep(pattern="testcontainers|docker-compose", glob="package.json")
If detected: run integration tests against real services, not just mocks. Reference 
testing-patterns
rules: 
integration-database
, 
integration-api
, 
data-seeding-cleanup
.

Phase 9 Gate

Do NOT proceed to Phase 9 (Documentation) if test-generator produced 0 tests. Return to Phase 5 and generate tests for the implemented code.

Key Principles

  • Tests are NOT optional — each task includes its tests, matched to change type (see matrix above)
  • Parallel when independent — use 
    run_in_background: true
    , launch all agents in ONE message
  • 128K output — generate complete artifacts in a single pass, don't split unnecessarily
  • Micro-plan before implementing — scope boundaries, file list, acceptance criteria
  • Detect scope creep (phase 7) — score 0-10, split PR if significant
  • Real services when available — if docker-compose/testcontainers exist, use them in Phase 6
  • Reflect and capture lessons (phase 10) — persist to memory graph

Related Skills

  • explore: Explore codebase before implementing
  • verify: Verify implementations work correctly
  • worktree-coordination: Git worktree management patterns
  • issue-progress-tracking: Auto-updates GitHub issues with commit progress

References

  • Agent Phases
  • Agent Teams Phases
  • Interview Mode
  • Orchestration Modes
  • Feedback Loop
  • CC Enhancements
  • Agent Teams Full-Stack Pipeline
  • Team Worktree Setup
  • Micro-Planning Guide
  • Scope Creep Detection
  • Worktree Workflow
  • E2E Verification