sdd

Archive completed tickets

User input: "$ARGUMENTS"

Performs comprehensive post-implementation code review of a completed ticket. Produces 12-section analysis with confidence scoring and recommendations. Reviews implementation against planning documents, evaluates code quality, identifies security vulnerabilities, assesses performance, and generates actionable recommendations categorized by severity (CRITICAL/HIGH/MEDIUM/NITPICK). Usage examples: - Basic: /sdd:code-review DEEPREV - Focused: /sdd:code-review DEEPREV --focus security - Force incomplete: /sdd:code-review DEEPREV --force

Ticket: $ARGUMENTS

Ticket: $ARGUMENTS

Update ticket planning documents and tasks to assign newly created specialized agents to appropriate work items. Use this Sonnet agent after creating custom agents from agent-recommendations.md. Examples: <example> Context: Custom agents have been created after recommendations user: "I've created the migration-specialist and cache-engineer agents, now update the ticket to use them" assistant: "I'll use the agent-assigner agent to update the planning docs and tasks with the new agent assignments." <Task tool invocation to launch agent-assigner agent> </example> <example> Context: User wants to integrate new agents into ticket workflow user: "Assign the new agents to the APIV2 ticket" assistant: "I'll use the agent-assigner agent to integrate the new agents into the ticket planning and tasks." <Task tool invocation to launch agent-assigner agent> </example>

Analyze ticket planning documents to recommend custom specialized agents that would meaningfully improve ticket success probability. Use this Sonnet agent after ticket planning is complete to identify high-value opportunities for agent specialization. Examples: <example> Context: Ticket planning documents are complete user: "Analyze the APIV2 ticket and recommend any specialized agents that would help" assistant: "I'll use the agent-recommender agent to analyze the ticket and identify opportunities for specialized agents." <Task tool invocation to launch agent-recommender agent> </example> <example> Context: User wants to improve ticket execution quality user: "What specialized agents should I create for the DOCKER ticket?" assistant: "I'll use the agent-recommender agent to recommend specialized agents based on the ticket requirements." <Task tool invocation to launch agent-recommender agent> </example>

Performs comprehensive post-implementation code review producing 12-section analysis with confidence scoring and categorized recommendations. This Sonnet agent analyzes completed tickets by examining planning documents, task files, and git diffs to generate detailed quality assessments. Use this agent after ticket execution to evaluate production readiness, identify risks, and provide actionable improvement recommendations. Examples: <example> Context: Ticket tasks completed, ready for review before PR user: "Run a deep code review on the AUTH ticket" assistant: "I'll use the code-reviewer agent to perform comprehensive analysis." <Task tool invocation to launch code-reviewer agent> </example> <example> Context: Focus on security aspects of implementation user: "Review the API ticket but focus on security concerns" assistant: "I'll use the code-reviewer agent with --focus=security to emphasize security analysis." <Task tool invocation to launch code-reviewer agent with --focus parameter> </example> <example> Context: Full analysis needed for complex feature user: "Complete code review for CACHE ticket - check everything" assistant: "I'll use the code-reviewer agent to perform full 12-section analysis." <Task tool invocation to launch code-reviewer agent> </example>

Use this agent when the user has completed verification of their work and is ready to commit changes with a proper Conventional Commit message. This agent should be used after the verify-task agent has confirmed all work is complete and verified. Examples: <example> Context: Developer has verified their work and is ready to commit. user: "The ticket has been verified. Please commit my changes." assistant: "I'll use the Task tool to launch the commit-task agent to create a proper commit for your verified changes." <commentary> The user indicates verification is complete and wants to commit, which is this agent's purpose. Use the Task tool to invoke commit-task. </commentary> </example> <example> Context: Developer wants to commit after successful verification. user: "Now that verification passed, let's commit the changes for ticket #123." assistant: "I'll use the Task tool to launch the commit-task agent to commit your verified changes with a proper commit message." <commentary> The user is ready to commit after verification, perfect use case for commit-task agent. Use the Task tool to delegate this task. </commentary> </example> <example> Context: Developer mentions they've finished work and testing. user: "I've finished implementing the feature and all tests pass. Ready to commit." assistant: "I'll use the Task tool to launch the commit-task agent to create a Conventional Commit for your verified work." <commentary> The user signals completion and readiness to commit. Use the Task tool to invoke the commit-task agent. </commentary> </example>

Research and plan epics for higher-order discovery work. Use this Sonnet agent when exploring new problem spaces, conducting research before knowing exact deliverables, or decomposing epics into tickets. This agent fills epic documents with research, analysis, and ticket decomposition. Examples: <example> Context: User has created an epic and needs content user: "I've scaffolded the api-redesign epic, now fill in the analysis" assistant: "I'll use the epic-planner agent to research and fill the epic documents." <Task tool invocation to launch epic-planner agent> </example> <example> Context: User wants to decompose epic into tickets user: "Break down the authentication epic into concrete projects" assistant: "I'll use the epic-planner agent to analyze and decompose the epic." <Task tool invocation to launch epic-planner agent> </example>

Orchestrates epics, tickets, and tasks for systematic software development. Use this skill when planning work, creating tickets, managing tasks, or executing development workflows. Includes scripts for scaffolding and status reporting, with Haiku agents for mechanical tasks and Sonnet agents for reasoning. All SDD data (epics, tickets, tasks, archives) lives at $SDD_ROOT_DIR, not in the repo.

Analyze session transcript logs to identify genuine reusable skill candidates across multiple tickets and sessions

7 hooks across 6 events