Productivity skills

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

personal-crm

Maintain a personal CRM — track relationships, last-touch dates, follow-ups owed, context from past conversations, and who deserves a check-in. Use this whenever the user says 'who do I owe a follow-up to,' 'when did I last talk to,' 'personal CRM,' 'track this contact,' 'log this conversation,' 'who should I check in with,' 'add [name] to my contacts,' or asks about their relationships and follow-up history. The skill maintains a structured `contacts/` folder with one markdown file per person, automatically surfaces follow-ups, and pulls context before any meeting.

121 repo starsObserved in 1 repos
Productivity

plan-roadmap

How to create plans and follow roadmaps

121 repo starsObserved in 1 repos
Productivity

project-flow-ops

Operate execution flow — triage tasks, manage priorities, keep progress structured. Use when the user needs backlog control, task planning, or workflow coordination across projects.

121 repo starsObserved in 1 repos
Productivity

session-learn

Extract reusable knowledge from a work session and save concepts, entities, corrections, patterns, ideas, decisions, and gaps to the wiki. Use when ending a session or when the user says to extract knowledge.

121 repo starsObserved in 1 repos
Productivity

step-back

Pause and critically reflect on the direction of the current conversation. Use this whenever the user says 'take a step back,' 'let's zoom out,' 'are we sure about this,' 'wait — am I missing something,' 'sanity check this,' 'pressure test this,' 'are we going down the wrong path,' or expresses doubt about where the discussion has gone. Also use proactively if you notice the conversation has accumulated assumptions that haven't been examined, or has drifted from the user's original goal. Output is a structured reflection — original goal, path taken, assumptions made, what might be wrong, and a recommendation.

121 repo starsObserved in 1 repos
Productivity

vertical-slice-planning

Use when a design spec is approved and needs to be decomposed into tracked, independently deliverable slices before writing implementation plans. Triggers on completed designs, multi-phase features, or when the user asks to break work into pieces with Linear tracking.

121 repo starsObserved in 1 repos
Productivity

approvals

Multi-step approval chains with requests, decisions, and temporary delegations.

120 repo starsObserved in 1 repos
Productivity

comms

Polymorphic conversation threads and messages for any entity

120 repo starsObserved in 1 repos
Productivity

decompose-task

Use when an existing task in an active Piyaz project carries scope larger than 13 points worth of work (composer's research brief raised the `oversize-task` flag, or the user explicitly says "split this task", "decompose RZE-42", "this task is too big", "break <taskRef> into smaller pieces"). Composer dispatches this from its oversize handler. Splits the parent into 2 to N child tasks, rewires every dependency edge touching the parent, and cancels the parent with rationale citing the children. Do NOT use for greenfield project decomposition (route to piyaz:decompose), for adding a new feature to an active project (route to piyaz:decompose-feature), or for refining a task without splitting it (route to the piyaz skill directly).

120 repo starsObserved in 1 repos
Productivity