Orchestrates and ships a milestone, release, issue set, or multi-workstream engineering goal through one manager and bounded parallel workers. Use when the user asks to manage a milestone, build a dependency graph, execute independent issues in parallel, coordinate threads, sessions, subagents, or worktrees, recover a…
Coordinate Supervisor, Worker, and Reviewer work through Auspex when a brief names an Auspex task, when handing work to another agent, or when reviewing shared task progress. Auspex remains the task state source; this skill is only the operating playbook.
Comprehensive task management using Taskwarrior CLI - add, modify, filter, complete, and sync tasks with support for projects, tags, priorities, due dates, dependencies, recurrence, and custom attributes (UDAs). Use when managing tasks, todos, or task lists including operations like creating tasks with attributes…
Elabora cronogramas físico-financeiros completos para obras de construção civil, integrando planejamento físico, financeiro e de recursos com base nas metodologias PMI/PMBOK, CPM, PERT, Linha de Balanço e EVM (Earned Value Management). Use quando o usuário pedir "cronograma de obra", "cronograma físico-financeiro"…
Manage a project kanban board stored as markdown files. Cards have status, priority, assignee, due dates, labels, and attachments. Columns are customizable.
Manages architecture project state in .arch/state.json and .arch/decisions.md. Use when reading or updating project phase state, checking architecture status or project progress, asking "what phase are we in", tracking component acceptance, recording or logging decisions, or validating phase transitions.
The planning front-door. Captures feature ideas and bugs as graded rows in the root INTAKE.md ledger. Use it when the user says "log an idea", "capture a bug", "add to the backlog", "note this down", "track this feature", or invokes /intake. Owns the requirements interview — fleshes out thin ideas, proactively…
Repairs a scratchboard kanban board that reads a repo's markdown tickets wrong, and names the field an agent writes to move a card. Use when tickets are missing from the board, when the board shows them in the wrong lanes or in Unmapped, when scratchboard reports it cannot read a ticket format, or when writing a…
Generate a "building in public" update from recent Linear activity and freeform notes. Use when the user wants to share what they've shipped, write a dev update, post about recent work, or draft a "here's what we built" post. Triggers on "farm-stand", "what did I ship", "write an update", "building in public", "what…
Craft a single, high-quality GitHub issue from a developer's description of a bug, unexpected behavior, or desired enhancement. Walks through reproduction, codebase exploration, and structured drafting so the issue is actionable on arrival. Use when user wants to file an issue, report a bug, request a feature, or…
Use when starting or closing an agent session, routing durable repository facts, maintaining status or task state, recording bugs, validating handoff conformance, or reconciling an older handoff layout.
Create, read, update, move, and manage kanban board feature files backed by markdown with YAML frontmatter. Use when working with kanban boards, task/feature tracking, .devtool/features/ directories, feature files with status/priority frontmatter, or any project management tasks involving markdown-based kanban…
A guided evening routine for a GTD task system, where GTD means sorting work into clear next actions, waiting items, and projects. It reviews the day, records results, and tidies unfinished work.
A tool for creating structured GitHub Issues in Chinese, with one section written for people and another organized for AI tools. GitHub Issues are records for bugs, tasks, and feature requests, and sub-issues break larger work into linked parts.
Spec-driven feature work in 4 phases — Specify, Design, Tasks, Execute — sized by complexity; atomic tasks and commits, Execute delegated to workers in waves plus an independent Verifier. Triggers on "specify/discuss feature", "design", "tasks", "implement", "validate", "verify work", "UAT", "record decision"…
Monitors analysis-doc lifecycle in all three lanes — EMERGING→PRODUCTION promotion, PRODUCTION→RETIRING/RETIRED retirement (replacement-readiness as robust community/vendor elements mature), and follow-lane upkeep (followed canons' advance triggers + liveness, per ABSORPTION-MAP.md).
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: