Stanshy/AgentHub

Development Plan Generator creates a standardized development plan from a proposal, including task breakdowns, specs links, and section 10 tracking tables. Use it when a sprint needs a structured implementation document.

Gate Record adds a gate review decision to section 10 of the dev plan. Use it to update the matching G0–G6 row with the date, decision, and review comment.

Harness Audit checks a Claude project’s CLAUDE.md, hooks, skills, and knowledge files against seven health principles. Use it to find missing coverage, stale docs, and rule gaps.

Internal Review runs an L1 checklist for code, specs, designs, functions, and document integrity, then records the result in the development plan. Use it to verify recent work and decide the next Gate step.

Knowledge Feedback scans child projects for recurring pitfalls and classifies them for company standard updates. Use it to prepare a cross-project report before any company knowledge files are changed.

PM Gate Review checks a gate submission against a 6-item checklist and produces a recommendation. Use it when evaluating whether a G2, G3, or G4 submission is complete and compliant.

Pitfall Record adds a lesson learned to the postmortem log with category, cause, fix, prevention, and a 14-day due date. Use it after incidents or troubleshooting to capture what happened and how to avoid it again.

Pitfall Resolve marks a matching postmortem pitfall entry as resolved. Use it when you need to search the log and update a record’s status from open to resolved.

Pre-Deploy generates a pre-launch checklist report before G5 submission. Use it to verify CI, environment variables, database, Docker, and security items before deploying.

Product Diagnosis uses a six-question framework to validate product direction before development starts. Use it to assess problem fit, user needs, scope, architecture alignment, and risk for G0 proposals.

Project Kickoff initializes a new project by creating CLAUDE.md, .knowledge files, roadmap docs, and git scaffolding. Use it when starting a project and you need the base structure in place.

SOP Deploy enforces a step-by-step pre-deploy checklist, task status check, and deployment gate recording before release. Use it when a deployment must not skip any checkpoint.

SOP Execute loads required rules, checks dependencies, and follows every checkpoint before marking a task done. Use it when a Claude Code agent must execute a task with strict step-by-step verification.

SOP Review guides an L1 code review by loading the task, checking standards, reviewing the diff, and making an approve or reject decision. Use it when you need a structured review that must not skip checkpoints.

Spec Update guides edits to files under .knowledge/specs/ with version bumps, changelog entries, and impact notifications. Use it when a spec file changes and related tasks need review.

Sprint Close merges a sprint branch back to the base branch, creates a release tag, and removes merged task and sprint branches. Use it after all gates are confirmed done.

Sprint Plan SOP loads sprint planning, postmortem, and architecture context before assessing task complexity and deciding whether to enter Plan Mode. It is used to decompose work and prepare task assignments.

Sprint Proposal generates a standardized sprint proposal document with goals, scope, process decisions, risks, acceptance criteria, and a G0 review section. Use it when planning a sprint from discussion notes.

Sprint Retro generates a sprint retrospective from section 10 of the dev plan and the proposal acceptance criteria. Use it after a sprint to summarize completion, quality, schedule, wins, and follow-up actions.

Task Approve marks a task as done after L1 review passes. Use it to update the task file, event log, and dev plan status.

Task Delegation creates a task table in section 6 of a dev plan and generates matching .tasks/sprint-N/TN-xxx.md files. Use it when you need to split planned work into assigned tasks with dependencies and timestamps.

Task Dispatch creates `.tasks/sprint-{N}/` task files from session instructions and appends them to the dev-plan. Use it to assign work, record dependencies, and keep sprint task tracking consistent.

Task Done marks a task as in_review and records the completion in the dev plan. Use it after verifying acceptance criteria and preparing the task for L1 review.

Task Start marks a task as in_progress when work begins. Use it to update the task file, record the start time, check dependencies, and handle the correct branch.

Task Status updates a task's status and appends an event log entry in .tasks files. Use it to record mid-task state changes and notes for tracked work.