potenlab-workflow

Plugin potenlab-workflow from marketplace potenlab-marketplace in potenlab/marketplace-potenlab. Commands read from the repo's manifest — 1 month ago.

Skills (10)

• complete-plan

  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

• developer

  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 age

• execute-phase

  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 (/

• generate-test

  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 da

• info

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

• plan-project

  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 creat

• review-plan

  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 updat

• run-test-all

  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, te

• run-test-phase

  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 ph

• verify-test

  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 syn

Slash commands (13)

• /potenlab-workflow:complete-plan

  Generate progress.json from finalized plans

• /potenlab-workflow:developer

  Post-completion adjustments tracked in changes.json

• /potenlab-workflow:execute-phase

  Execute all tasks in a phase with wave-based parallel coder agents (max 4 per wave)

• /potenlab-workflow:generate-test

  Generate Vitest test files from test-plan.md into root tests/ directory

• /potenlab-workflow:hello

  Confirm potenlab-workflow is installed and active

• /potenlab-workflow:info

  Display Potenlab workflow overview and status

• /potenlab-workflow:plan-project

  Orchestrate project planning with specialist agents (includes test plan generation)

• /potenlab-workflow:review-plan

  Edit existing plans based on user feedback

• /potenlab-workflow:run-test-all

  Run all Vitest tests and generate test.result.json

• /potenlab-workflow:run-test-phase

  Run Vitest tests for a specific phase

• /potenlab-workflow:security-resolve

  Resolve pending security findings from security-list.json

• /potenlab-workflow:security-review

  Run a comprehensive security audit on the project and generate security-list.json with findings

• /potenlab-workflow:verify-test

  Detect code changes and update tests to stay in sync

Subagents (9)

• backend-specialist

  Creates backend-plan.md by reading dev-plan.md and translating its backend tasks into detailed schema definitions, migration SQL, RLS policies, query specifications, and connection strategies. Uses MCP Postgres to discover current database state and enforces Supabase best practices. Does NOT write c

• frontend-specialist

  Creates frontend-plan.md by reading dev-plan.md and translating its frontend tasks into detailed component specifications, file paths, props, patterns, and implementation guidelines. Uses shadcn MCP to discover components and enforces Vercel React best practices. Does NOT write code — coder agents e

• high-coder

  Executes complex, multi-file tasks from dev-plan.md. Uses Opus for deep reasoning on tasks requiring cross-file coordination, architectural awareness, and intricate business logic. Handles the heavy lifting that small-coder cannot. Only writes code — does NOT update progress.json.

• progress-creator

  Creates progress.json by reading dev-plan.md, frontend-plan.md, and backend-plan.md. Parses all phases and tasks into a structured JSON tracking file that coder agents use to identify pending work and dependencies. Runs AFTER all plans are finalized.

• qa-specialist

  Generates feature tests for a Next.js + Supabase app using Vitest. Reads test-plan.md and produces .test.ts files that verify behavior via database operations and RLS policies against a running Supabase local instance. Does NOT test UI, does NOT use Playwright, does NOT create or alter tables.

• security-specialist

  Performs comprehensive security audits on repositories by scanning for vulnerabilities across OWASP Top 10 categories. Reads source code, configuration files, environment setup, Supabase RLS policies, API routes, and dependencies to produce security-report.md with findings, severity ratings, and rem

• small-coder

  Executes small, isolated tasks from dev-plan.md. Uses Sonnet for fast, cost-efficient implementation of single-file changes, minor fixes, and simple feature additions. Refuses large or multi-file tasks — escalates them back to the user. Only writes code — does NOT update progress.json.

• tech-lead-specialist

  Creates dev-plan.md as the single source of truth by reading ui-ux-plan.md from the ui-ux-specialist. Translates design decisions, wireframes, component specs, and accessibility requirements into a minimal, phased development checklist with verifiable tasks. Does NOT create progress.json — that is h

• ui-ux-specialist

  Creates ui-ux-plan.md with comprehensive design strategy, user research, wireframes, and design system documentation. Ensures WCAG 2.1 AA/AAA accessibility compliance and beautiful, intuitive interfaces.\n\nExamples:\n\n<example>\nContext: User has a PRD file and needs a UI/UX design plan.\nuser: \"

Similar plugins