.Agent

How to detect GitHub CLI and set up a full GitHub-based development workflow

How to maintain a lightweight work log for Manager Agents to track high-level decisions during project execution. Use when you need to document key choices, rationale, and project status manually throughout the workflow.

How to implement features using Test Driven Development (Red-Green-Refactor)

How to manage transitions between agent roles and generate handoff prompts for new threads

How to validate features through functional testing and produce a validation report

Enforce Security Gates A/B/C across architecture, PR review, and release sign-off using severity-based blocking rules.

How to map product features to technical solutions and define a tech strategy

Standardize PR closure workflow for GitHub tickets with required linkage, test evidence, and issue close-out comments. Use when finishing implementation and preparing to close a ticket.

How to prioritize backlog tickets and organize them into sprints using MoSCoW

How to present deliverable information as visually appealing ASCII summaries

How to convert product requirements into executable backlog tickets with DoD

Standardizes the creation of "Source of Truth" Markdown briefs in .agent/temp for assigning tasks to Developer Agents.

Enforce QA final gate for milestone release with dependency verification, full matrix execution, and sign-off reporting. Use when QA must wait for implementation tickets to close before validating release readiness.

Produce concise operational status reports for multi-agent delivery including done/open/blocked counts, dependency bottlenecks, and immediate next actions. Use for periodic stakeholder updates during milestone execution.

Execute one GitHub ticket end-to-end with a consistent operational contract (STARTED, BLOCKED, DONE), evidence posting, and closure hygiene. Use when an agent picks up a specific issue for implementation.

Operate GitHub Projects boards with clear status flow, entry/exit policies, field hygiene, and automation rules. Use when configuring a board, running daily execution, or fixing status drift across tickets.

How to initialize a project repository with proper structure and configuration

How to support non-GitHub tracking systems (Jira, Linear, Trello, Asana) via manual sync

How to conduct a product discovery interview and produce a Product Vision document

How to enforce local self-correction (linting, compiling, testing) before requesting peer review. Use when an agent finishes coding a feature and needs to validate it locally to ensure it is grammatically and syntactically flawless.

Generate visual UI mockups from product vision for human review before development begins

Default deployment documentation gate for Apps Script/web-app projects. Use automatically on every deploy/redeploy task and whenever deployment URL/version references may change.

How to automatically audit the docs/ directory and remove/archive outdated Markdown files to prevent agent context rot at the end of a sprint. Use during Step 7 (Release) or when finalizing a milestone.

Monitor milestone execution health by detecting stale tickets, blocked queues, missing ownership signals, and timeline risk. Use during active delivery windows to keep work moving and escalate risks early.

How to coordinate between multiple AI agents working simultaneously on the same project through a shared message board. Use when agents need to post status updates, log decisions, ask questions, or report blockers.

How to generate a lightweight AGENTS.md table of contents file to provide progressive disclosure of the repository to other agents. Use when scaffolding a new project or updating core architectural boundaries.

Run parallel development safely using Git worktrees with one isolated branch per ticket. Use when multiple agents need to work concurrently in the same repository without branch conflicts.

Create and manage GitHub epics as parent issues with clear outcomes, sub-issue decomposition, dependency mapping, and closure criteria. Use when defining a new initiative, restructuring epic scope, or reviewing epic health.

Ensures deliverables and structured content are presented in clear, copy-friendly Markdown code blocks for easy human consumption.

Write execution-ready GitHub tickets with clear scope, acceptance criteria, test plan, metadata, and dependencies. Use when creating new issues from requirements, refining vague backlog items, or standardizing issue quality.

Run recurring backlog triage for GitHub issues and projects to keep priorities, scope, and blockers current. Use during weekly planning, release risk review, or backlog cleanup sessions.

Systematic code review checklist for quality, security, and maintainability

Plan and manage GitHub milestones with due dates, realistic scope, and outcome-based delivery targets. Use when preparing sprint/release slices, balancing capacity, or recalibrating timeline commitments.

Orchestrate GitHub issue dependency execution across multiple agents with explicit start gates, unblock signals, and progress transitions. Use when a milestone has chained tickets and agents must start only after dependency tickets are closed.