domain
265Agent
How engineering skills should consume this repo's domain documentation.
981 tagged agentic-workflow, measured the same way as everything else here.
Browse within: agentic-coding 132agent-orchestration 106github-copilot 91agentic-engineering 86ai-coding-assistant 86ai-assistant 65ai-coding-agent 59ai-personas 59agentic-framework 56agentic 52agent-framework 39anthropic-claude 35claude-ai 34antigravity 32
Agent
How engineering skills should consume this repo's domain documentation.
Agent
Work items for this repo live in Clew, not GitHub Issues.
Agent
Matt Pocock's skills speak in terms of five canonical triage roles. Clew does not have external tracker labels; represent triage roles as Clew tags except where noted.
danweinerdev/claude-sdd-planner
Agent
Part of sdd-planner
Adversarial fresh-eyes code reviewer. Receives the diff only — no plan, spec, or design — and deliberately hunts for the scenarios intent-aware reviewers forgive: concurrency, retries, encoding, security, production failures, maintenance traps, and unknown-unknowns. Every finding is a concrete scenario, not a vague…
danweinerdev/claude-sdd-planner
Agent
Part of sdd-planner
Reviews implementation plans and design documents for completeness, feasibility, convention compliance, and gap analysis. Invoke before approving a plan, when a plan is revised, or when a design needs a structural sanity check. Returns findings with severity and a verdict of Approve or Revise.
danweinerdev/claude-sdd-planner
Agent
Part of sdd-planner
Gathers context from planning artifacts, codebase, and the web to inform planning decisions. Invoke at the start of /brainstorm, /specify, /design, /plan, /poke-holes, or any skill that needs a compound view of existing research, specs, designs, plans, and related code before new work begins.
Agent
Executes an approved agentmaster-plan plan end to end. Use after accepting a plan at the Plan Ready for Review prompt — "execute the plan", "run the plan", "build it". Dispatches one implementer subagent per conflict-free parallel group, gates on per-task verification, then performs the full frontier code review…
Agent
Cost-tiered planning coordinator. Use to produce an implementation plan, spec, or root-cause investigation before code changes — multi-file features, bug hunts, refactors, dependency problems. Reasons and decides only; delegates all repository and dependency evidence to scout and code-analyst subagents, stress-tests…
Agent
Transcript-driven analyze-fix-verify loop for the agentmaster skill suite itself. Use after a pipeline run leaves artifacts behind — .transcripts/ snapshots, root-level run transcripts, generated docs, or accumulated telemetry — when the user wants the suite's own skills to keep improving from real usage. Grades…
Agent
Part of kenspc
INTERNAL: Part of /kenspc-task-review orchestration. Requires REVIEWREPORTS structured CONTEXT input from the calling skill — standalone invocation will fail the prerequisite check. Do not auto-delegate.
Agent
Part of kenspc
INTERNAL: Part of /kenspc-task-review orchestration. Requires REVIEWREPORTS and ACCOUNTABILITYLIST CONTEXT — standalone invocation will fail the prerequisite check. Do not auto-delegate.
Agent
Part of kenspc
INTERNAL: Part of /kenspc-task-implement orchestration. Requires validated task document path — standalone invocation will fail the prerequisite check. Do not auto-delegate.
Agent
Part of phase-gate
Adversarial post-implement sweep agent. Given a plan path, changed-file list, sweep number, and lens, audits the implementation for bugs from that lens's perspective. Flag-only — never modifies code. Scope bounded to changed files + 2-hop dependencies. One finding per real issue; no style/naming/formatting feedback.
Agent
Part of phase-gate
Bounded coding agent. Executes a single plan phase against an explicit file manifest. Catalog-aware — reads bug-catalog.md before editing to avoid known recurring pitfalls. Returns a structured diff + decision record; flags out-of-scope findings instead of improvising. Never touches files off-manifest. Never spawns…
Agent
Part of phase-gate
Context-isolated rubric evaluator spawned by /implement's phase-gate for each semantic row in verification.jsonl. Reads a single deliverable and a specific rubric (≥3 binary items), finds evidence quotes per rubric item, returns structured pass/fail. Fresh agent per row — no context from the implementer — to prevent…
Agent
"Is this correct?" — Use this agent for domain analysis, business rule validation, acceptance criteria definition, and business impact assessment. Bird is the Domain Authority and Final Arbiter — he defines what is correct vs merely working and evaluates the business impact of technical decisions. Use via /team for…
Agent
"What could break?" — Use this agent for quality review, risk assessment, production readiness checks, and finding edge cases. Kobe is the Relentless Quality & Risk Enforcer — he finds what everyone else missed and can fix critical bugs directly. Use via /team for orchestrated workflows, or directly for standalone…
Agent
"How should we build this?" — Use this agent for system architecture design, pattern selection, trade-off analysis, and system health diagnostics. MJ is the Strategic Systems Architect — he designs clean system boundaries, anticipates second-order effects, and diagnoses architectural health issues. Use via /team for…
Agent
Use this agent when you want to eliminate code duplication across your codebase. Examples: Context: User has just written several similar functions and wants to clean up duplication. user: 'I just added these three validation functions that seem really similar' assistant: 'Let me use the code-deduplicator agent to…
Agent
Use this agent when you need expert guidance on HTML and CSS layout techniques, responsive design, flexbox implementation, or solving browser-specific styling issues. Examples: Context: User is struggling with creating a responsive navigation bar that collapses on mobile. user: "How can I create a navigation bar that…
Agent
Use this agent when TypeScript tests are failing and need to be fixed, when test suites need cleanup to remove redundant tests, or when new tests need to be added after discovering bugs that weren't caught by existing coverage. Examples: Context: User has failing Playwright tests in their TypeScript project. user: 'My…
martin-francois/symphony-trello
Agent
The order of work for any task: what to read first, how to scope a change, how to verify, and how to commit and open pull requests. Topic-specific rules live in the pages linked under References.
martin-francois/symphony-trello
Agent
Agent "maintaining-agent-docs" from martin-francois/symphony-trello, covering maintaining agent docs, progressive disclosure contract, what may be added to agents.md (allowlist), what must not be added to agents.md (denylist) and where to put new guidance (decision tree).
martin-francois/symphony-trello
Agent
This file is the source of truth for the structure and maintenance approach.
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: