wigtn-plugins
wigtn · wigtn/wigtn-plugins
This Claude Code plugin orchestrates a complete AI-native development workflow, from PRD generation and screen specifications to parallel implementation, quality analysis, and verified commits using 11 specialized agents.
Claude Code Plugins for AI Native-based Engineer
Preview
What you can do with it
- Generate a structured Product Requirement Document (PRD) and task plan for a new project idea.
- Implement a project with parallel backend, frontend, AI, and operations teams, managed by the plugin.
- Perform comprehensive quality analysis and automated commit after passing configured checks.
Safety check
No risky patterns found in the files we scanned.
Automated scan of the repo files. Always review code you run.
From the README
WIGTN Plugins
One plugin. 11 agents. From idea to a verified commit.
Why WIGTN-Coding?
Without this plugin: You open Claude Code → write a vague prompt → get generic code → spend 30 min fixing → repeat.
With WIGTN-Coding:
You run /prd → get a structured contract → generate screen specifications when needed → implement → commit only after the configured checks pass.
What it does
WIGTN Plugins is a Claude Code plugin with 11 specialized agents for requirements, architecture, implementation, and review. It uses parallel work only where tasks are independent, and carries one contract from PRD through commit.
/prd "SaaS dashboard with OAuth" → Contract-based PRD + task plan
/screen-spec dashboard → (if UI) IA + flow + screen spec + clickable wireframe HTML
/implement --parallel → Backend + Frontend + AI + Ops teams build simultaneously
/auto-commit → Findings rollup + objective checks + commit
Quick Start
# Install
/plugin marketplace add wigtn/wigtn-plugins
/install wigtn-plugins
# Try it — this is the full workflow
/prd landing page for an AI startup with modern design
/implement ai-landing
/auto-commit
That's it. The plugin handles PRD generation, 4-category quality analysis, architecture decisions, design style selection, parallel build, code review, and commit.
The Pipeline
┌─────────────────────────────────────────────────────────────────────────────┐
│ /prd "SaaS dashboard with OAuth" │
│ │
│ 1. Context Gathering ─── scan project structure, tech stack, package.json │
│ 2. AskUserQuestion ───── Scale Grade? (Hobby / Startup / Growth / Enterprise) │
│ 3. PRD Generation ────── PRD_{feature}.md (7 sections, Gherkin stories) │
│ 4. Task Planning ─────── PLAN_{feature}.md (phases + tasks) │
│ │
│ ┌─── prd-reviewer — 4 adversarial lenses ────────────────────────────┐ │
│ │ Phase 0: Context Harvest (CLAUDE.md, code patterns, deps) │ │
│ │ Phase 1: PRD Structure Parsing │ │
│ │ Phase 2: ═════════════ 4 ADVERSARIAL LENSES ══════════ │ │
│ │ │ Completeness │ Feasibility │ Security │ Consistency │ │ │
│ │ │ FR/NFR/edge │ stack fit │ OWASP │ naming/arch │ │ │
│ │ │ cases, dups │ blast radius│ auth/z │ PRD↔code │ │ │
│ │ Phase 3: Cross-Category Synthesis (compound risks) │ │
│ │ Phase 4: Quality Gate ─── PASS / WARN / BLOCKED │ │
│ └────────────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────────────┘
│
BLOCKED → stop
│ PASS / WARN
▼
┌─────────────────────────────────────────────────────────────────────────────┐
│ /implement ai-landing │
│ │
│ ┌─── DESIGN PHASE ──────────────────────────────────────────────────┐ │
│ │ ═══════════════ 3 AGENTS IN PARALLEL ═══════════════ │ │
│ │ │ Agent A │ Agent B │ Agent C │ │ │
│ │ │ PRD load + │ architecture-decision│ Project scan + │ │ │
│ │ │ quality gate │ Mono/Modular/MSA │ gap analysis │ │ │
│ │ ══════════════════════════════════════════════════════════════ │ │
│ │ │ │ │
│ │ Team Allocation ─────── pattern match files → teams │ │
│ │ api/, services/ → Backend │ │
│ │ components/, app/ → Frontend │ │
│ │ ai/, llm/ → AI Server │ │
│ │ Dockerfile, CI/ → Ops │ │
│ │ │ │
│ │ Design Discovery (Frontend only, if no existing style) ──────── │ │
│ │ VS technique: 4 questions → suitability % per style → select │ │
│ │ │ │
│ │ ✋ CHECKPOINT: AskUserQuestion ── proceed / review / cancel │ │
│ └───────────────────────────────────────────────────────────────────┘ │
│ │
│ ┌─── BUILD PHASE ─── team-build-coordinator ────────────────────────┐ │
│ │ │ │
│ │ Phase 0: Setup ─── SHARED_CONTEXT_{feature}.md + PLAN ledger │ │
│ │ Context Harvest: sample existing code → learn patterns │ │
│ │ │ │
│ │ Phase 1: Foundation (if Backend + dependents exist) │ │
│ │ Backend writes: DB schema, shared types, API contracts │ │
│ │ ↓ unblocks other teams │ │
│ │ │ │
│ │ Phase 2: ════════════ UP TO 4 TEAMS IN PARALLEL ════════════ │ │
│ │ │ BACKEND │ FRONTEND │ AI SERVER │ OPS │ │
│ │ │ backend- │ frontend- │ ai-agent │ gen │ │
│ │ │ architect │ developer │ │ pur │ │
│ │ │ │ + style guide │