Opt-in OpenSpec-mode authoring for Chorus PM workflows on dsh. Runs inline three-check detection for the local openspec CLI, scaffolds openspec/changes/ / on disk, and mirrors Markdown files into Chorus document drafts via chorus mcp call --arg-file (package-local chorus-mcp-call.mjs wrapper as fallback). Required…
Opt-in OpenSpec-mode authoring for Chorus PM workflows in Pi. Detects the local openspec CLI, scaffolds openspec/changes/ / on disk, and mirrors Markdown files into Chorus document drafts via chorus mcp call --arg-file (bash chorus-mcp-call.sh wrapper as fallback). Required reading for the proposal, develop, and yolo…
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
Execute work through an OverClick MCP board. The board's MCP server is overclick (tools mcpoverclick); overclock is the IDE — one letter apart, different systems. Never guess the prefix. Use whenever an OverClick server is connected and the user mentions cards, tasks, missions, a card ID, or asks to register, claim…
Operate Forge's singular global Main Agent during Product Genesis and portfolio-level discovery. Use when turning a rough idea into a named, revisioned Project Charter; pressure-testing intent with at most two consequential questions per turn; doing bounded public research; presenting an exact user approval target…
Implement, review, or evolve Forge's cross-role Project orchestration contracts across the singular Main Agent, one Project Agent per Project, Task Workers, reviewers, users, and system authority. Use for architecture, persistence, API, migration, policy, or acceptance work involving Product Genesis, Charter approval…
Operate the singular Project Agent for exactly one Forge Project after Charter-backed handoff. Use when verifying Project startup, doing bounded research, drafting revisioned Project Documents and Decisions, proposing or reconciling an execution baseline, creating and managing traceable Tasks, coordinating independent…
ClickUp CLI for managing tasks, sprints, comments, statuses, Docs, and archiving. Use when the user needs to interact with ClickUp — creating/editing/archiving tasks, checking sprint status, adding comments, linking PRs, managing Docs and pages, or searching tasks. Includes a generic clickup api passthrough covering…
Use beads (bd) for persistent task tracking in coding projects. A git-backed issue tracker designed for AI agents with dependency graphs, hierarchical tasks, and multi-agent coordination.
Work with DuneBoard task files in a repository. Use when Codex needs to plan, take, create, update, block, release, or close DuneBoard work; run pnpm dune; or preserve DuneBoard Markdown task history.
Bootstrap DuneBoard in a local repository. Use when adding a DuneBoard board to a project, initializing tasks/, installing agent guidance, registering the project in the local DuneBoard UI selector, or making a project self-describing for future agents.
Organize an existing local project into DuneBoard tasks and specs. Use when the user asks to clean up local todo notes, scattered Markdown specs, issue notes, backlog files, roadmap docs, or agent-written plans into a simple DuneBoard board without unnecessary process.
Close out the active task: review the result against the plan, archive to PROGRESS.md, and reset CURRENT.md. Run after you've reviewed and committed the work.
Work through BACKLOG.md item by item with the user — verify what can be checked against the code, surface duplicates and contradictions, and reorder. Use when the backlog has grown long enough that you no longer trust it.
Audit the briefs for a project when it feels muddled, stalled, or you've lost the thread. Reports what's out of shape and asks one question to drive reprioritization.
A daily worklist and priority manager that stores tasks and background information in Markdown files. It separates ongoing context from individual things that need to be done.
Research a software task and return a reviewable implementation plan before coding. Use when a user request needs codebase investigation, target files, approach, alternatives, risks, todos, and verification guidance.
Polish a completed code change with a bounded independent review protocol. Use after implementation and before final approval or PR to review intent, acceptance criteria, non-goals, diff, relevant files, verification, and previously rejected findings.
Quench a plan or design by asking the smallest useful product/design questions in dependency order and hardening decisions before implementation. Use when a plan has ambiguous acceptance criteria, unresolved choices, or branching decisions that code inspection cannot answer.
Inspect, validate, operate, and develop a self-contained Microsoft To Do Safe MCP skill with bundled server. Use for Microsoft To Do task/list management, safe backup/plan/preview/apply workflows, MCP startup checks, token-safe diagnostics, and deciding whether to run doctor/test/typecheck/build.
Use when working with Loci tickets — starting, updating, and completing tickets via the loci CLI. Covers workflow, CLI commands, doc conventions, and assignee/status formats.