marketplace-potenlab

Executes all tasks in a specific phase using wave-based parallel execution (max 4 agents per wave). Spawns small-coder and high-coder agents based on progress.json complexity. Updates progress.json after EACH wave so completed tasks immediately unblock dependents. Accepts phase number as argument (/execute-phase 3) or asks via AskUserQuestion. Triggers on: execute phase, run phase, build phase, develop phase, start phase.

Generates Vitest test files from test-plan.md using the qa-specialist agent. Reads the test plan and vitest best practices, then spawns qa-specialist agents to produce .test.ts files in the root tests/ directory for features, shared tests, and Supabase integration tests. Tests verify behavior via database operations and RLS policies — no UI testing. Triggers on: generate test, generate tests, create tests, write tests, test generation.

Orchestrates sequential project planning. First validates user intent via AskUserQuestion (MANDATORY), then spawns ui-ux-specialist to create ui-ux-plan.md, then tech-lead-specialist to create dev-plan.md from ui-ux-plan.md, then spawns frontend-specialist and backend-specialist in parallel to create their detailed plans from dev-plan.md, then spawns qa-specialist to create test-plan.md from dev-plan.md and backend-plan.md. Triggers on: plan, create plan, plan project, project plan, full plan, prd to plan.

Runs ALL Vitest tests across /features, /tests, and /supabase directories. Executes tests via npx vitest run, collects results, and generates test.result.json (replaced on every run). Uses qa-specialist to analyze failures and provide actionable feedback. Triggers on: run test all, run all tests, test all, vitest all, run tests.

Runs Vitest tests for a specific phase chosen by the user. Reads test-plan.md to identify phases, asks user which phase to run via AskUserQuestion, executes only those test files, and generates test.result.json (replaced on every run). Uses qa-specialist to analyze failures. Triggers on: run test phase, test phase, run phase test, test specific phase.

Verifies and updates tests after code changes. Detects what changed (git diff, changes.json), compares against test-plan.md, then spawns qa-specialist agents to update test-plan.md and edit/create test files in /features, /tests, /supabase. Use after /developer or manual changes to keep tests in sync. Triggers on: verify test, verify tests, sync tests, update tests, check tests, test verify.

Finalizes the planning phase by spawning progress-creator agent to read all plan files (dev-plan.md, frontend-plan.md, backend-plan.md) and generate progress.json — the structured task tracker used by coder agents. Run this AFTER /plan has completed. Triggers on: complete plan, finalize plan, create progress, generate progress, progress json.

Post-completion development skill for adjustments and changes after all phases are done. Accepts change requests from arguments (/developer fix the login button) or via AskUserQuestion. Analyzes existing code and plans, creates change tasks in docs/changes.json, spawns small-coder and high-coder agents in parallel, and tracks all results in changes.json. Triggers on: developer, dev, adjust, change, fix, tweak, modify, post-dev.

Display an overview of the Potenlab plugin ecosystem. Use for "info", "ecosystem", "about potenlab".

Reviews and edits all existing plan files based on user feedback. Accepts feedback from arguments (/review-plan change X to Y) or via AskUserQuestion. Same sequential flow as /plan (ui-ux -> tech-lead -> frontend+backend parallel) but EDITS existing plans instead of creating from scratch. Also updates progress.json if it exists. Triggers on: review plan, edit plan, update plan, change plan, revise plan, adjust plan.

Orchestrates coder agents to execute phase tasks. Analyzes progress.json to determine parallel execution. Usage: /developer [phase] - if no phase specified, asks user. Spawns multiple agents for independent tasks. Triggers on: develop, developer, start phase, execute phase, build phase.

Orchestrates complete project planning from PRD. Spawns frontend, backend, and UI/UX specialists in parallel, then consolidates with tech-lead-specialist. Creates comprehensive dev-plan.md and progress.json in /docs directory. Triggers on: plan project, create dev plan, project planning, full plan, prd to plan.

Orchestrates plan reviews based on user needs. Spawns frontend-reviewer and/or backend-reviewer as needed, then syncs changes with tech-reviewer. Usage: /review-plan [user needs]. Triggers on: review plan, review frontend, review backend, sync plans, update plan.

Track progress with auto-flow execution. Use for "checkpoint", "progress", "status", "start CP", "complete", "resume".

Systematic debugging workflow. Use for "debug", "fix bug", "not working", "error", "broken".

Initialize project with PRD and checkpoints. Use for "init project", "new project", "start project".

Quick task without full workflow. Use for "quick", "just add", "small change", "simple fix".

Revert changes when implementation fails. Use for "rollback", "undo", "revert", "go back", "start over".

Save or resume work context. Use for "save", "pause", "resume", "continue", "stopping".

Initialize project with PRD and checkpoints. Use for "init project", "new project", "start project".