implement

Orchestrates full-product feature implementation using parallel backend, frontend, and test agents.

4|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/VoxTechnologies/transmute-framework --skill implement-voxtechnologies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/VoxTechnologies/transmute-framework/tree/main/skills/implement
Command: npx skills add https://github.com/VoxTechnologies/transmute-framework --skill implement-voxtechnologies

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating the implementation of every feature in a PRD across backend, frontend, and testing layers is error-prone and often results in stub components, missing states, and orphaned code. This Skill automates Stage 5 of the Transmute Plan Casting pipeline by orchestrating agent teams to build the complete product with quality gates between features. ## Core Features & Use Cases - Feature Queue Orchestration: Builds a dependency-ordered implementation queue from the PRD feature map (P0 through P3), splitting large features into sub-features and handling blocked or circular dependencies. - Per-Feature Agent Cycle: Spawns backend, frontend, and E2E test teammates sequentially for each feature, with a lead-run quality gate enforcing typecheck, tests, traceability, and anti-stub scans. - Session Recovery & Completion: Resumes interrupted sessions from plancasting/_progress.md, re-runs features flagged by the Stage 5B audit, and produces a final implementation report with launch readiness assessment. - Use Case: After completing PRD, scaffolding, and CLAUDE.md setup, run this Skill to implement all 23 features of your product — each with real backend logic, composed frontend components, and Playwright E2E tests — ending with 100% PRD coverage. ## Quick Start Ask the agent to run Stage 5 feature implementation from the PRD and build the complete product.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement all features from a PRD automatically?

Run Stage 5 of the Transmute pipeline, which reads the PRD feature map, builds a dependency-ordered queue, and spawns backend, frontend, and E2E test teammates per feature. Each feature passes a quality gate before the next begins, ending with a full-product completion sequence.

What prerequisites are required before running feature implementation?

Stage 5 requires completed PRD and BRD directories, plancasting/tech-stack.md, a populated CLAUDE.md Part 2, the scaffold manifest from Stage 3, and real credentials in .env.local with no placeholder values. Missing prerequisites cause the stage to stop with a specific error.

Does the implementation skip lower-priority features like P2 or P3?

No. All priority levels P0 through P3 are implemented; priorities only determine build order, not scope. Features are never skipped, only reworked if the Stage 5B audit flags gaps.

How does session recovery work if implementation is interrupted?

The orchestrator reads plancasting/_progress.md and performs a positional scan, skipping Done features and resuming In Progress ones from the first incomplete layer (backend, frontend, or tests). Features marked for re-implementation by Stage 5B are rebuilt from scratch.

Why does the quality gate reject features with stub components?

Anti-stub gates grep for placeholder patterns like TODO markers and Coming soon text, and verify every component is imported somewhere. Features failing these scans are sent back to the responsible teammate to prevent incomplete code reaching the Stage 5B audit.