Plugins

2 plugins

Task Execution Workflow

Load a plan, execute tasks with verification, and track progress via issues.

10 skills · plugin

Superpowers Sage

Modern WordPress development with Sage, Acorn & Lando. Workflow skills: /architecture-discovery, /plan-generator, /building, /designing, /verifying (+ /architecting compatibility alias), with design tool integration, content modeling, visual verification, and comprehensive hooks.

36 skills · plugin

Results for “plan-verification”

10 skills

Turns a mature product plan into a rough implementation plan with high-level steps, maturity and verification marks, and a risks section.

Verifies each step of a rough implementation plan against source code and current documentation, attaching proof and marking steps as verified or unverified.

Get Shit Done - Full project planning and execution workflow. Handles project initialization with deep context gathering, automated research, roadmap creation, phase planning, and execution with verification.

More results

Compare, cross-review, and merge competing plans from multiple agents into one executable direction with a clear handoff.

066 Capa 982d53c7

Guides CAPA effectiveness assessment with verification methods, SMART criteria, and closure requirements.

Reviews development plans for gaps, hidden assumptions, critical misses, and XP violations, then presents prioritized findings for confirmation.

Continues deep iteration on an existing planning document: detects explicit file-loading intent, provides status summaries, and supports on-demand in-depth exploration.

Manage CAPA investigations, root cause analysis, corrective action planning, and effectiveness verification for medical device quality management systems.

20.4k · bundle

Routing-first visual approval gate for AI agent plans, markdown specs, and diffs. Use when a human needs to review a concrete plan before execution, inspect a targeted diff in a browser, mark up a spec/PRD/architecture note, or set up the review loop on Claude Code, Gemini CLI, Codex CLI, or OpenCode. Route planning/spec creation to `task-planning` or `ralph`, broad PR-policy review to `code-review`, rendered-UI critique to `agentation`, and fresh-session browser verification to `browser-harness`.

theheavenlyd3mon

Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request (issue, ticket, or request) from intake through planning, gates, implementation, review, verified PR, and authorized post-merge release. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For change-request / issue-to-PR work, conditionally loads a 9-phase journey with gates, delivery packet, and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer. The journey is not loaded for plain fixes, refactors, or reviews that lack an issue/ticket trajectory.