Product & Planning

harshanandak Bundle

Everyday single-issue CRUD over the `forge issue` verbs: create/update/show/list/search/close/reopen/comment, set priority/labels/assignee, claim or release one issue, add/remove dependency edges, plus backlog `stats`. Use for ANY routine one-off issue op: "create an issue/bug/task for X", "update/edit issue <id>", "close or reopen this issue", "comment a handoff note on <id>", "list/filter open bugs by status/label/priority", "bump this to P1", "reassign to alice", "mark <id> blocked by <id>". Also the parity floor migrating off a Beads-style tracker (label/reopen/delete map to forge equivalents). Single-operation plumbing only. Does NOT choose, rank, or explain the next issue to work on or why it's blocked (use triage-ready); does NOT run claim-then-prove-lease-ownership safety (use claim-safety); does NOT drive an issue through the plan->dev->validate->ship pipeline or open a PR (use smith or stage skills); does NOT report the current stage or what's in flight (use status).

a-v-ershov Skill

Commit the current uncommitted changes: read the diff, group files by logic rather than path (a definition change split from its ripple of usage updates), write conventional-commit messages in English — with the [T###] backlog task id where one applies — and commit on the current branch, never branching, pushing, merging, amending or adding AI-attribution trailers. By default only the files this session touched are committed. Invoked by run-task for checkpoint commits and by cut-release for the release commit; otherwise use ONLY on the user's explicit request to commit — finishing a task or a review is not such a request. /commit [--dry-run] [--single] [--all] [--message <msg>]

a-v-ershov Bundle

Drive ONE task through the full development cycle: the implementer builds it, a separate fresh verifier independently proves the acceptance criteria, its findings go back for exactly one fix round, the static gate plus this task's scoped test selection must be green (the whole suite is never run here), the human accepts the work or it is auto-accepted, and a checkpoint commit carrying the task id lands. Two entry points: a task id from the backlog, or a free-form request it files itself with origin: adhoc. A small, obvious change can take the quick lane instead. Anything the single fix round leaves open escalates to needs_human. Sequential, single working tree, current branch.

a-v-ershov Skill

Work through the development plan: take tasks from .dev-skills/build-plan/ one at a time and run each through run-task. The order is deterministic, not a judgement call — the ready task (status todo, all blocked_by done) with the lowest id; no parallel tasks, one working tree. It refuses to start when the spec has moved ahead of the plan and offers plan-development first, skips tasks another session has claimed, and never retries a needs_human task. By default it runs straight through, pausing only for a real reason; one-at-a-time and thinned acceptance are opt-in. Resumable — the backlog is the source of truth. Use after plan-development. It writes no code and duplicates no cycle.

a-v-ershov Bundle

Interview the human to extract maximum context before and during spec work — a relentlessly curious discovery grill that turns a short brief into a rich, shared understanding of what to build. Two roles: as the FIRST step of create-project-spec it runs a full intake interview and writes .dev-skills/project-spec/project-brief.research.md plus a short human summary, which every later phase reads as settled intent; on demand it is a reusable grill any phase can invoke, scoped to a fork blocked on context only the human holds. Captures intent, audience, scope, constraints and developer preferences as soft priors. It does NOT validate the idea or define features.

a-v-ershov Skill

Turn the finished project spec into a buildable backlog. Use after setup-dev-environment, as the planning step of the build phase: it reads the committed feature set, the user flows, the architecture and the dev-architecture, and emits a kanban backlog under .dev-skills/build-plan/ — one markdown file per task plus a derived board.md and a short plan.summary.md. Tasks are coarse on purpose: the backlog holds at most 15 open ones. When the repo already has working code it plans only the gap. Re-run after the spec changes and it amends instead — task deltas, never a regenerate; re-run with 'consolidate' and it merges the open backlog back under the ceiling. Run before build-tasks.

a-v-ershov Skill

Build one backlog task's feature in the working tree. Use as the implementation stage of the build loop — normally spawned fresh per task by run-task, or standalone on a task id. It reads the task's description and acceptance criteria, builds on the current branch following the project's CLAUDE.md and existing patterns, writes its journal into the task file as it goes, then self-verifies against .dev-skills/project-setup/verification.md and gets the static gate plus this task's scoped test selection green before handing off. It never runs the whole suite, does not run the verifier and does not commit.

fabioc-aloha Skill

Reviews an AI-related decision for stakeholder impact, privacy, responsibility, transparency, contestability, and reversibility.

jsuvic Skill

Use when a stakeholder request is rough, ambiguous, or underspecified and needs clarification before planning, writing a spec, or creating issues.

qa-aman Skill

Write a Product Requirements Document (PRD). Use when the user says "write a PRD", "document this feature", "product requirements for X", "write requirements", "I need a PRD", "pitch this feature", or wants to formalize a feature or product idea into a structured doc - even if they don't explicitly say "PRD".

qa-aman Skill

Write OKRs (Objectives and Key Results). Use when the user says "write OKRs", "help me set goals", "create objectives and key results", "quarterly goals", "team OKRs", "I need to define success for this quarter", "Doerr method", or wants to translate a strategic direction into measurable targets - even if they don't explicitly say "OKRs".

qa-aman Skill

Synthesize pilot observations into structured debrief reports and spec updates. Use this skill when: - A pilot has completed and you have observation notes, tickets, or feedback transcripts - You need to turn messy pilot data into actionable spec changes - You want to generate edge case user stories from field observations - You need negative acceptance criteria from pilot bugs - You want a structured debrief report for stakeholder communication

qa-aman Skill

Quality gate for product specifications before stakeholder review. Use this skill when: - A spec draft is ready and you want to validate it before sending to Engineering, Design, and QA - You want to check a spec against your template's completeness rules - You need to catch vague language, missing sections, or gaps before review - You want a pass/fail scorecard with specific fix suggestions

qa-aman Skill

Prioritize a feature backlog or list of ideas. Use when the user says "help me prioritize", "prioritize this backlog", "RICE score these", "MoSCoW", "opportunity solution tree", "what should we build first", "rank these features", or has a list of items and needs to decide order - even if they don't explicitly say "prioritization".

qa-aman Bundle

Run structured product thinking exercises before writing a spec. Use this skill when: - You need to think through a feature idea before writing a PRD - You want to run the 11-star experience exercise for a feature - You need a positioning statement using Geoffrey Moore's framework - You want to define product principles and success vision for a new feature - You have a raw feature idea and need to turn it into a structured brief

qa-aman Skill

Audit a roadmap or backlog to distinguish outcomes from outputs. Use when the user says "outcome vs output", "escaping the build trap", "are we building the right things", "roadmap review", "feature factory", "output-driven team", "we keep shipping but nothing changes", or wants to shift focus from shipping features to delivering value - even if they don't explicitly say "outcome vs output".

qa-aman Skill

Run product discovery to identify what to build. Use when the user says "product discovery", "how do I know what to build", "validate this idea", "talk to customers", "are we building the right thing", "discovery process", or wants to reduce the risk of building something users don't want - even if they don't say "discovery".

qa-aman Skill

Generate structured weekly or fortnightly status updates for leadership and stakeholders. Use this skill when: - You need to prepare a weekly or fortnightly status report - You want to summarize recent progress across git commits, tickets, and spec changes - You need a formatted update ready for Slack, email, or a stakeholder meeting - You want multi-project updates in one report

qa-aman Skill

Generate user research interview scripts using Mom Test principles. Use this skill when: - You are preparing for user interviews or pilot observation sessions - You need a question bank organized by behavior, context, pain points, and workflow - You want interview guides that avoid leading questions and hypotheticals - You need per-persona interview guides - You are preparing for field visits or pilot debriefs

qa-aman Skill

Build Opportunity Solution Trees using Teresa Torres' framework for structured product discovery. Use this skill when: - You need to map a desired outcome to opportunities, solutions, and experiments - You want to decide WHAT to build next based on user research and discovery data - You have workshop findings, pilot feedback, or user research to structure into actionable options - You need a visual tree diagram showing the path from outcome to testable experiments

whyzsm Bundle

Prefer `skillhub` for skill discovery/install/update, then fallback to `clawhub` when unavailable or no match. Use when users ask about skills, 插件, or capability extension.

kyrie66nb Skill

Initialize a PRD (Product Requirements Document) for structured ralph-loop execution

peterfei Skill

OKR（目标与关键结果）的结构化思维工具。基于6个一手来源的深度调研， 提炼6个核心原理和完整的操作协议。 触发词：「OKR」「目标管理」「关键结果」「目标对齐」「Objective」「Key Result」「季度目标」。

ramboz Bundle

Lightweight baseline elicitation pass that fills in `docs/product-vision.md` and the five `docs/architecture.md` elicitation slots after `scaffold-init`. Auto-triggers when you say set up project vision, elicit architecture, define what we're building, run the vision wizard, refresh the project pitch, or capture product scope. Defers to any other installed skill whose description identifies it as handling vision elicitation, product discovery, project framing, or product scope capture — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `init` skill. Do not use for: ad-hoc brainstorming with no `docs/product-vision.md` slot to write into; silently overwriting vision content the user has already hand-edited (the re-run protocol's divergence detection handles that — see the Re-run protocol section below); spec authoring (use `/jig:spec-workflow`); seeding ADRs for already-named decisions (use `/jig:adr-workflow new`).

djalmajr Bundle

Structures large initiatives into a decomposed backlog with roadmap, dependencies, and verification. Generates an overview file plus individual story files with tasks. Use when work requires several coordinated stories, has dependencies between deliveries, or needs a roadmap.

djalmajr Bundle

Create static, browser-based UI prototypes with a zero-build stack built from z-proto, HTM UI, Tailwind CSS v4, Preact/htm, and preact-iso. Use when asked for an HTML prototype, clickable browser mockup, interaction demo, or stakeholder flow that runs without a backend or build pipeline. Component, theme, and API implementation lives in the complementary htm-ui skill. For prototypes in a design tool (Paper, Figma, Pen.dev, Penpot), use agile-design.

djalmajr Bundle

Structures new and vague problems into clear intake documents. Use when the problem is not yet mature enough for the backlog, when someone brings an idea or need without defined scope, or when you need to decide what the next artifact in the flow should be.

djalmajr Bundle

Plans sprint by selecting items from backlog, defining objective, capacity, and execution order. Use at the beginning of a work cycle to align what will be done.

djalmajr Bundle

Maps multi-phase trajectories with dependencies into clear, sequenced roadmaps. Use when work has multiple phases that need sequencing, when decisions today affect future decisions, when stakeholders need to see the whole journey, or when external dependencies exist. Applicable regardless of total duration — a 4-week multi-phase initiative benefits as much as a quarterly roadmap.

eugenezhangco-spec Skill

Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".

wirasm Skill

Interactive PRD generator - problem-first, hypothesis-driven product spec. Use when the user wants to create a PRD, write a product or feature spec, scope a new product, or invokes $prp-prd.

wirasm Bundle

Creates an implementation-ready plan for a feature, bug fix, refactor, or chore from a PRD, issue, document, or description using codebase evidence, first-principles reasoning, and conditional root-cause analysis, research, or spikes. Publishes issue-derived plans back to their source issue. Use when the user asks to "plan this feature", "plan this bug fix", "plan issue X", "create an implementation plan", "turn this PRD into a plan", investigate how a change should be built, link related plans, or invokes $prp-plan.

wirasm Skill

Autonomously owns one workstream from an issue, PRD, document, existing plan, or free-form request through planning, implementation, pull request, independent review, corrections, and green CI. Always use when the user asks to implement or ship work end to end, take an issue or idea to a reviewed PR, run plan to PR, invokes $prp-issue, or when prp-orchestrate needs an end-to-end delivery engine.

wirasm Skill

Maintains PRD implementation-phase status and artifact links. Always use when a PRP workflow records a planned, implemented, or merged phase in its source PRD, when the user asks to update PRD progress, or when the user invokes $prp-prd-update.

baixuanzhu Bundle

当用户说"开始项目""敏捷""Sprint""待办""Backlog""用户故事""迭代""架构决策""ADR""C4""需求变了""要改故事""依赖检查"或进入含 agile-docs/ 目录的项目时触发。不适用于：纯运维部署、需要与 Jira/Trello 深度集成。

baixuanzhu Bundle

当用户说"开 Sprint""规划迭代""关闭 Sprint"或 using-agile 路由到此，且 PRODUCT-BACKLOG.yaml 已有条目时触发。