Use when a user wants to design one bounded feedback loop from a goal, assess or upgrade an existing Agent Skill with feedback loops, distill a completed conversation or work record into a candidate workflow and, when compatible, a loop-aware Skill, build an accepted Loop Craft JSON definition, or check an existing…
First-principles assumption auditor. Deconstructs any decision or belief into irreducible premises, classifies each assumption (fact / convention / belief / interest-driven), ranks them by fragility × impact, and rebuilds conclusions from verified ground truth. Bilingual: responds in the user's language (Chinese or…
Use this skill when user asks to create, write, or draft a PRD (Product Requirements Document). Generates structured PRDs with governance framework, problem statements, business goals, use cases, and functional requirements.
A software-development process for turning tasks into checkable work agreements, staged implementation, quality checks, and evidence-based completion reviews.
Use when the user asks for deep business review of PRDs, requirement documents, product specs, feature proposals, or business process docs. Focus on understanding business model, modules, data relationships, flows, permissions, states, rules, omissions, contradictions, ambiguities, implementation risk, and…
Use when initializing a new project, setting up documentation structure, or creating project scaffolding with AGENTS.md and docs/ folder hierarchy for feature-based documentation. Also use when user asks to setup project documentation, generate docs structure, or create issue documentation for bugs and root cause…
Mandatory dispatch preflight before any subagent delegation. Use before the first child-work call in every task, and when starting Codex work that needs an explicit Direct vs Single/Parallel/Sequential choice: code edits, debugging, reviews, repo exploration, multi-file changes, ambiguous scope, high-risk judgment, or…
A guided problem-diagnosis skill for situations involving a business, product, content, career choice, partnership, or difficulty getting work done. It turns a person's account of the situation into a structured discussion and possible next steps.
Run a structured pre-task alignment interview for complex or ambiguous work. Use when the user asks to be grilled, wants questions before execution, requests requirements discovery or scope alignment, or when unresolved goals, constraints, tradeoffs, risks, or acceptance criteria could materially change a complex…
Roadmap and analysis of potential improvements, design trade-offs, and feature priorities. Use when planning new features, evaluating what to build next, or understanding why certain approaches were chosen or rejected.
You have access to Siftable, a shared evidence-backed work graph connecting human planning, executable agent work, projects, knowledge, relationships, calendar, code, governed actions, and verification.
Decompose complex work into a small ordered council of Pantheon gods. Use for tasks that combine research, implementation, design, review, or scheduling.
A planning guide for deciding when to split work between the main agent and smaller worker agents. It also describes how to define each worker's file boundaries and check its result.
Default cost/complexity routing table for the batuta conductor. Read at bootstrap as a starting point, validated against the live provider catalog, then stored as the per-workspace loop configuration; the stored workspace override is authoritative afterwards.
A product-management guide for turning an idea or existing material into a defined product and its written plan. It supports step-by-step discussion, decisions, and user confirmation.
Stress-test a plan or design against domain language, docs, and code. Ask hard questions one at a time. Update CONTEXT.md and ADRs as decisions crystallize. Use when you already have a draft plan or spec and want to find gaps before implementation.
Lead complex engineering work: own architecture, risk, contracts, delegation, and acceptance. Use for multiple engineering workstreams, substantial integration, or explicit chief-engineer leadership. Do not add orchestration to a simple linear task or pure research without engineering integration.
Product Spec Builder that helps PMs generate clear, structured, testable PRDs. Creates both full and lightweight specs for any product or platform with a guided step-by-step workflow. Output in English Markdown format.
Create one or more tasks via wade task create — for a single bug/feature OR a full plan/PRD breakdown. This is the STANDALONE task-creation workflow, used whenever the user directly asks to create a task/issue outside a wade plan session. Assesses scope, proposes a single- or multi-issue breakdown with reasoning, gets…
A structured process for checking whether a product idea is worth building. It researches the market, competitors, and technical feasibility, then records a recommendation and the assumptions behind it.
Use for governed software work that needs source-of-truth checks, routing, token/context governance, branch/PR discipline, validation honesty, and release readiness. Do not use as approval for writes, installs, migrations, broad plugin use, external tool activation, or global config changes.
★not rated 5 1mo agoA60 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: