Claude Skills by bendusz

> **Update (2026-07-07, v0.9.3):** the project was relicensed from MIT to GPL-3.0-or-later. > References to MIT below reflect the license at the time this plan was written. > **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking. **Goal:** Build a generic, public, self-contained Claude Code plugin (`pm-skill`) whose `project-mana...

Use for end-to-end software project delivery, covering discovery, specification, planning, sign-off, decomposition into stories, implementation, review, verification, and shipping. Acts as a Project/Product Manager and delegates all code to specialist subagents.

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /poteto:architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /poteto:arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /poteto:create-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.

Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.

Use for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /poteto:maintain-verification-skill or \"audit the verify skill\".

Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.

Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'

Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /poteto:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.