Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate…
Festival task execution specialist. Use when working through festival tasks, marking completion, committing with traceability, managing task state (completed/blocked/reset), and advancing through sequences. Follows the fest next → work → complete → commit loop.
🌌 PARA Workspace is an open-source workspace framework that defines how humans and AI agents organize knowledge and collaborate on projects. It ships as a repo containing a kernel (constitution), CLI tools, and templates — which generates workspaces where you actually work.
Developer agent for exactly ONE GitHub issue, dispatched by the /pm-dispatch PM loop. Implements the issue end-to-end in a dedicated worktree — branch, code, tests, changeset, push, draft PR — and returns a structured JSON report to the PM. Use only with a single fully-specified issue as input; never for open-ended or…
A helper agent that updates a work-plan document using the actual status of related work plans. A work plan is a project record of tasks, blockers, and progress.
Universal implementation and progress tracking expert using artisan agent pattern. Analyzes task specifications, implements solutions following project patterns, validates against acceptance criteria, then automatically updates completion status. Use PROACTIVELY for systematic task implementation with integrated…
Technical/Solution Architect agent that reviews backlog, advises on feature integration, evaluates technical approaches, and coordinates with Scribe for backlog management. Routes to specialist sub-agents based on request type.
Campaign brain for driving a whole tdmcp feature BACKLOG to completion (not one wave). Reads the backlog markdown + the campaign ledger.json, reconciles them against what is already shipped in the tree, computes the next ready WAVE (dependencies + shared-schema-first satisfied), assigns version targets, and proposes…
Transforms one-line product ideas into comprehensive validated feature backlogs with pain points, competitive analysis, and MVP candidates. Use when user says: feature backlog for [idea], explore [idea], pain points for [idea].
Agent "team-workflow" from timharris707/modeldeck, covering team workflow — repo bindings, tracker binding, verify commands, the decider and docs home.
Issues/tickets for this repo are tracked as 4x feature YAML files under .4x/features/{feature-id}.yaml, managed via the 4x CLI — not GitHub Issues. (.4x/settings.json's issuetracker.enabled can additionally link a feature to a GitHub/GitLab issue when configured — check settings before assuming plain local-only.).
The working surface for {{NAME}}'s repo, and the canonical one: every other tool's instruction file is generated from this file plus the rules in .agents/rules/, so none of them can drift. Read this first each session.
A weekly review tool for newly signed contracts that records where the deal differed from the company’s playbook. It saves the surrounding context while the details are still fresh.
Use this agent when you need to analyze and prioritize GitHub issues for a React project, particularly when deciding what to work on next. The agent will examine all open issues, analyze their priority based on multiple factors, and provide actionable recommendations with clear justifications. Examples:\n\n \nContext…
You ship one curated-factory Wave per run from the curation backlog. You implement and label; you NEVER merge — the wave-merge executor re-verifies your PR mechanically (scope ledger and required checks) and performs the merge. Live GCP apply-smoke is retired; do not terraform apply against terradart-validate.
A project-management agent for chip-design work that tracks requirements, risks, progress, milestones, interfaces, and quality gates. It also consults a built-in technical knowledge base for design decisions.
Owns the Zulip communication and owner-control plane for the current Claude Code session. Use proactively when work should stay synchronized with a Zulip topic.
Manage GitHub project board operations for moving issues between status columns.
★not rated 24 todayA16 tokens
originalMIT
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: