Productivity skills

Browse reusable Agent Skills, each with a clear purpose and practical guidance.

design-interrogation

Relentlessly interview the user about a plan, design, or feature spec to surface unresolved decisions, hidden assumptions, and edge cases. Use when the user says "grill me", "stress-test this plan", "poke holes in my design", "what am I missing", or before committing to a plan that feels under-examined. Unlike /specs (which produces artifacts) this skill produces clarity — it's a thinking tool. Also use proactively in the Research phase when a design doc has implicit decisions that need to be made explicit.

252 repo starsObserved in 1 repos
Productivity
GitHub

issues-from-assessment

Convert a `/cd-test-architecture` assessment into a parent + Phase-tagged child issues on the tracker the operator points at (ADO, GitHub, GitLab, Jira). Dispatches by parent URL host to the tracker's own CLI (`az boards`, `gh`, `glab`, `acli`). When no parent URL is given, or when the required CLI is not installed, falls back to local plan files under `./plans/<workflow>/` after informing the operator. Multi-workflow: called by `/test-improve` (Phase 3), via its own `--workflow` namespace so memory paths and tracker labels never collide.

252 repo starsObserved in 1 repos
Productivity
GitHub

issues-from-plan

Break a plan into independently-grabbable GitHub issues. Use when the user says "create issues from this plan", "break this into tickets", "file issues", or wants to distribute plan steps across a team.

252 repo starsObserved in 1 repos
Productivity
GitHub

openprd-harness

驱动 OpenPrd 工作区完成 clarify、synthesize、diagram、freeze、handoff、change、tasks 和验证。

252 repo starsObserved in 1 repos
Productivity
GitHub

openprd-requirement-intake

OpenPrd 需求入口与 PRD 分流 skill：判断用户可见需求类型和内部 L0/L1/L2 路由码，决定直接澄清、mini-plan 或正式 PRD，并选择通用 / 面向个人消费者场景 / 面向企业服务场景 / 以 Agent 为主要使用场景的 PRD 视角。对用户复述时不要直接把 consumer / b2b / agent 当展示词；这些枚举值只用于内部记录和命令。

252 repo starsObserved in 1 repos
Productivity
GitHub

review-summary

Generate a compact summary of the most recent code review results and save it for future sessions. Use this at the end of a coding session after /code-review has run, or when the user says "summarize the review", "save the results", "generate a summary", or wants to preserve review context before closing a session.

252 repo starsObserved in 1 repos
Productivity
GitHub

specs

Collaborative workflow for producing the three specification artifacts (intent, architecture notes, acceptance criteria) that describe a change and its goals before any implementation begins. Its value is resolving ambiguity with a human before build starts — not synthesizing edge cases. Use when starting any new feature or behavior change — do not write code until artifacts pass the consistency gate. BDD/Gherkin scenarios are authored later, per slice, in /plan.

252 repo starsObserved in 1 repos
Productivity
GitHub

decision

Capture a project decision as an ADR-style record in decisions/NNNN-slug.md — context, options considered, the call, consequences, status. Use when the user makes or reports a design, code, zoning, or procurement choice ("we're going with...", "the client decided..."), when an analysis surfaces options that force a choice, or to supersede an earlier decision. Records reasoning — current facts live in PROJECT.md via /project-dossier.

251 repo starsObserved in 2 repos
Productivity
GitHub

feature-task-planning

功能任务规划。将技术方案拆解为细粒度、可执行的开发任务清单 (Task List)，每个任务适配 TDD 流程。

251 repo starsObserved in 1 repos
Productivity
GitHub

master-schedule

Silent setup check. Verifies master-schedule.json exists and the sheet is accessible. If not, copies the template sheet to the user's account and writes master-schedule.json. Called automatically by other skills before reading or writing product data.

251 repo starsObserved in 1 repos
Productivity
GitHub