Use when the user wants to proactively push a project forward by implementing its next feature. Reads project artifacts (specs' "future work" sections, README, TODOs, recent commit trajectory, codebase gaps), infers candidate features, asks the user to pick one, then implements it on an isolated branch with…
Assess coupling with the Balanced Coupling model (integration strength, distance, volatility). Use when judging whether coupling is balanced or risky, scoring the couplingbalance dimension, or deciding what to flag as structural risk. Highest risk is high strength + high distance + high volatility together. NOT…
Use when the user wants to plan, dispatch, review or deploy software sprints in a multi-chat orchestration pattern — running parallel multi-agent work across isolated git worktrees without context bloat in long Claude sessions. Skill provides a portable workflow with auto-discovery of project profile, modular addons…
A Fable-5-inspired work-discipline protocol adapted for Codex CLI and Codex desktop. It uses a plan gate, small-card execution, adversarial self-check, real-product verification, context hygiene, and checkpoint autonomy. Activate ONLY on an explicit request — the user names the mode ("use fable mode", "enable…
Use when a task needs the full OpsX workflow from exploration through change/spec, planning, implementation, verification, archive, and branch finish using OpenSpec and superpowers.
Personal growth gap retrospective. 5-category sweep ranked by decision-velocity signals; each top gap launched with a Deep Research / NotebookLM prompt + 4 multiple-choice questions grounded in your own codebase (your files + ADRs are the ground truth, not the AI's knowledge). Step 0 Action Audit refuses new items if…
An end-to-end workflow for building mobile and web products, from clarifying requirements and designing prototypes to coding and testing. It coordinates several design, architecture, coding, and testing tools.
PRD-driven delivery loop with a token-lean audit trail (requests → decisions → specs → tasks → commits). All docs/ log access goes through ./scripts/owl. Use for any feature, bug fix, or change in a repo using ATHENA docs/.
Use a fresh task profile and a four-level policy to turn material ambiguity into a precise, self-contained prompt without asking the user to make technical choices the agent can investigate.
Guides agents through a 7-phase rigorous feature development workflow with 4 independent cross-verification passes: systematic self-review, cold-context code review (reviewer sees no design docs — finds design-level blind spots single reviewers miss), behavior-preservation diff, and cross-repo impact scan. Use this…
Product Office Hours — structured product thinking partner. Startup mode: six forcing questions on demand reality, status quo, specificity, narrowest wedge, observation, future-fit. Builder mode: design thinking for side projects, hackathons, learning, open source. Produces a design doc, never code. Use when asked to…
Run a moderated panel discussion across multiple Solo MCP projects and AI agents. Spawns 3 panelists (personas, cross-project lenses, or hybrid), runs N rounds with synthesis between rounds, delivers final verdict. TRIGGER when user says "brainstorm with panel", "get multiple perspectives", "debate this", "/panel", or…
A coordinator for complex, multi-stage projects that span conversations and tasks. It helps discuss requirements, create execution plans, assign roles, track progress, and preserve useful project knowledge.
A workflow that uses Claude Code sub-agents to carry out a product requirements document, or PRD, one user story at a time. A PRD is a document describing what a product or feature should do.
Reviews code diffs after implementation, auto-fixes safe issues, and runs specialist security and architecture reviewers on large diffs. Also triages issues and PRs when the user mentions them. Not for exploring ideas or debugging.
Prioritize features, tasks, bugs, initiatives, or any backlog of items using the VERDICT framework. Use this skill whenever the user wants to decide what to build first, triage a backlog, sequence a roadmap, compare multiple initiatives, or score items against a consistent rubric. Also trigger when the user says…
Full feature development lifecycle — PRD, critical review, task breakdown, implementation, and quality gates. Use when the user provides a feature description and wants to go all the way from idea to working, reviewed, tested code.
Turn a user-supplied idea.md into a complete, credible new open-source software project, from an approved private plan through implementation, selected documentation and site surfaces, the ecosystem's real distribution form, a verified v0.1.0 release, and PR-only repository governance. Use for end-to-end creation of a…
Run the 4CO-OP multi-stage coding pipeline for a feature request, including the nightly monitor window and performance logging.
★not rated 2 4mo agoA29 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: