Productivity skills

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

project-brain

Triggers (all require explicit user request — do NOT activate just because a brain/ folder exists): (1) The user wants to set up project-level memory ("set up project brain", "scaffold project context", "init project brain", "建项目脑"). (2) The user is in a directory containing brain/ AND explicitly asks to resume / continue / load the project / check status / "what's the state of this project" / "继续这个项目". (3) The user signals window switch / context compaction ("switch windows", "context's getting full", "I'll head out", "压缩了", "切窗口") — write a HANDOFF before they leave. (4) The user says "update the project brain" / "let's record this" / "更新项目脑" — propose a list with reasons; user approves per item. (5) The user mentions multiple parallel workstreams / 多线程项目 / 多任务并行 — enable Multi-workstream Mode (METHODOLOGY §3.5). Do NOT auto-activate from casual conversation — explicit user request required. See METHODOLOGY.md.

178 repo starsObserved in 1 repos
Productivity
GitHub

using-long-task

Use when starting any session in a long-task project - routes to the correct phase skill based on project state

178 repo starsObserved in 1 repos
Productivity
GitHub

bdd-collaboration

Use when facilitating BDD collaboration between developers, testers, and business stakeholders. Use when running discovery workshops and example mapping sessions.

175 repo starsObserved in 3 repos
Productivity
GitHub

git-storytelling-branch-strategy

Use when planning git branching strategies or managing branches for development. Helps create clear development narratives through effective branch organization and workflow patterns.

175 repo starsObserved in 3 repos
Productivity
GitHub

codex-brainstorm

Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.

175 repo starsObserved in 2 repos
Productivity
GitHub

create-request

Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard. Not for: feature-level problem-space analysis (use req-analyze for 1-requirements.md lifecycle doc), tech specs (use tech-spec), code implementation (use feature-dev). Output: request ticket with status tracking, referencing parent tech-spec.

175 repo starsObserved in 2 repos
Productivity
GitHub

git-storytelling-commit-strategy

Use when planning commit strategies or determining when to commit changes. Helps developers commit early and often to tell the story of their development process.

175 repo starsObserved in 2 repos
Productivity
GitHub

post-dev-recap

Post-development recap wrapper. Use when: AI/Codex just finished implementing a feature and the user wants a guided walkthrough with scope detection + doc generation + follow-up Q&A. Not for: generating only a doc (use /recap-doc), Q&A over an existing recap (use /recap-ask), technical share-out (use /tech-brief), first-principles reasoning of an existing doc (use /fp-brief), general code tracing (use /code-explore). Output: ScopeReport → briefing-recap-<date>.md → interactive Q&A session.

175 repo starsObserved in 2 repos
Productivity
GitHub

tech-brief

Technical briefing for developer sharing. Use when: sharing implementation findings with technical colleagues, post-development knowledge transfer, documenting what was built and why. Not for: PM/CTO summary (use project-brief), first-principles reasoning (use fp-brief), design-phase specs (use tech-spec). Output: 6-section technical brief with source provenance.

175 repo starsObserved in 2 repos
Productivity
GitHub