bounded-work-item
Execute one bounded CCB work item and report evidence without changing workflow authority.
3.27k repo starsObserved in 2 repos
Productivity
Productivity skills
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
ccb-self-chain
Diagnose and repair CCB ask/job/message/reply/artifact/callback lineage. Use for missing replies, incomplete artifacts, pending callbacks, retry/resubmit/ack decisions, reply delivery problems, or work-chain resume advice.
3.27k repo starsObserved in 2 repos
Productivity
clarification-broker
Compress planner candidate questions into a compact frontdesk-facing clarification batch and normalize answers back to planner.
3.27k repo starsObserved in 2 repos
Productivity
orchestration-bundle-candidate
Select one route and return one adaptive one-to-four-workgroup bundle candidate as reply-only evidence.
3.27k repo starsObserved in 2 repos
Productivity
plan-readiness-review
Review planner task packets for readiness without rewriting authoritative task state.
3.27k repo starsObserved in 2 repos
Productivity
plan-tree
Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next state; resume work from TODO/handoff state; move resolved questions into decisions; promote ideas into formal plan artifacts; or keep plan documents and file-structure planning internally consistent without making this project-specific.
3.27k repo starsObserved in 2 repos
Productivity
planner-closure-backfill
Produce one revision-fenced Planner backfill proposal for either a Detailer replan or task-set closure, with compact Frontdesk status evidence.
3.27k repo starsObserved in 2 repos
Productivity
epic-create
Authoritative protocol for authoring an Epic body — the creation-side dual of `ticket-create` + entry partner of `epic-review`/`epic-resolution`. Enforces: epic body = problem-scope + intended-solution (NOT pseudo-subs / ACs); ACs live in the SUB tickets; subs are LINKED via `update_issue_relationship` + added incrementally; the body MUST NOT hardcode a sub-list (it stales out → FAIL). Triggers: before creating an Epic (a parent issue labeled `epic`) via `create_issue`, or before decomposing one into sub-tickets.
3.23k repo starsObserved in 1 repos
Productivity
epic-resolution
Closeout protocol for parent epics — answers "we resolved all epic subs, are we done now?" with a structured matrix + verdict recommendation (close / keep open / create missing subs / retire-supersede). Sibling to epic-review (which handles entry); this is the exit gate. Triggers: Use this skill when the last required sub of an epic closes, when a team member claims an epic is complete or substrate-side complete, before closing an epic as COMPLETED, or when a peer broadcasts an epic-readiness signal that needs reconciliation against parent ACs.
3.23k repo starsObserved in 1 repos
Productivity
epic-review
Authoritative protocol for pre-work review of epics. Six-stage gating chain — roadmap fit, approach elegance, source discussion mapping, sub-structure coherence, prescription layer, avoided-traps completeness — posted as a structured comment on the epic ticket. Per-agent-per-epic one-shot; subsequent sub pickups cite the prior review. Triggers: Use this skill when an agent is about to pick up its first sub from an unreviewed epic (per model-identity). Also use when a user explicitly requests an epic review, or when an epic is freshly filed and a reviewer pre-validates before any sub pickup begins.
3.23k repo starsObserved in 1 repos
Productivity