implement-guide

Drafts implementation plans, stress-tests them with a parallel review council, then implements phase by phase.

1|1|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/nexuslabs-ai/nexus --skill implement-guide-nexuslabs-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-guide
Source: https://github.com/nexuslabs-ai/nexus/tree/main/.agents/skills/implement-guide
Command: npx skills add https://github.com/nexuslabs-ai/nexus --skill implement-guide-nexuslabs-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into code without a vetted plan leads to wrong assumptions about existing code, over-engineering, and missed edge cases. This Skill enforces a disciplined workflow: draft a phased plan, have four independent review lenses attack it against the actual codebase, then implement one verified phase at a time. ## Core Features & Use Cases - Structured Planning: Researches requirements (including GitHub issues via gh), technology versions, and existing architecture, then produces a phased plan with file structure, risks, and verification steps. - Parallel Review Council: Fans the draft plan out to four concurrent subagent lenses (codebase reality-check, architecture & ripple, simplicity & reuse, edge cases & states) that return severity-tagged findings with file:line evidence. - Reflex-Driven Implementation: Implements phase-by-phase in the main session using a reflex checklist mapped to project rules (guard clauses, nx: Tailwind tokens, Storybook story tests, ripple-effect sweeps), with mandatory typecheck, lint, and commit after each phase. - Use Case: Given GitHub issue #42 requesting a new Dialog size variant, the Skill drafts a phased plan, the council catches that an existing size helper already covers the case, the plan is revised, and each phase is implemented, verified, and committed in sequence. ## Quick Start Ask the agent to plan and implement the feature described in GitHub issue 42 using the implement-guide workflow.

Frequently Asked Questions about implement-guide

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

FAQPage Schema
How do I plan and implement a feature from a GitHub issue?▼

The workflow fetches the issue with `gh issue view`, researches the technology context, explores existing architecture, and drafts a phased plan. After a review council validates it and the user approves, each phase is implemented, typechecked, linted, and committed in order.

What is a plan review council in AI coding workflows?▼

It is a set of four concurrent subagents that each attack a draft plan from one lens: codebase reality-check, architecture and ripple effects, simplicity and reuse, and edge cases. Each returns severity-tagged findings with file:line evidence, and the main session accepts or rejects each finding before finalizing the plan.

Does this workflow delegate code implementation to subagents?▼

No. Only the plan review is delegated to parallel subagents. Drafting the plan and all implementation stay in the main session, which writes code one phase at a time and commits after each phase.

How are React components tested in this workflow?▼

Components are tested through Storybook stories with play functions imported from storybook/test, covering variants, sizes, disabled states, interactions, and data attributes. Hooks and utilities use *.test.ts files with @nexus_ds/test-utils instead.

When should I not use a phased plan-and-implement workflow?▼

It is overkill for trivial one-line fixes or typo corrections where planning and council review cost more than the change itself. It fits multi-file features where wrong assumptions about existing code carry real rework risk.