Manages quality gates and checkpoints to ensure work meets standards before proceeding to next phases. Use when you need to verify work quality, set quality standards, or decide if work is ready to proceed. Defines quality criteria, checks work against criteria, and makes go/no-go decisions.
/plugin marketplace add lexicalninja/secret-agents/plugin install lexicalninja-my-little-scrum-team@lexicalninja/secret-agentsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
When: After specification is created Criteria:
When: After tasks are broken down Criteria:
When: After design specifications are created Criteria:
When: After code is implemented Criteria:
When: After code review Criteria:
When: Before deployment Criteria:
## Quality Gate: [Gate Name]
### Gate Type
[Specification / Task Breakdown / Design / Implementation / Review / Deployment]
### Work Reviewed
[What work was reviewed]
### Quality Criteria
#### Criterion 1: [Description]
- **Status**: [Met / Not Met / Partial]
- **Notes**: [Notes on criterion]
#### Criterion 2: [Description]
- **Status**: [Met / Not Met / Partial]
- **Notes**: [Notes on criterion]
### Overall Assessment
**Status**: [Approved / Changes Requested / Blocked]
### Issues Found
- [Issue 1]: [Description and severity]
- [Issue 2]: [Description and severity]
### Feedback
[Feedback for improvements]
### Decision
**Can Proceed**: [Yes / No / After Changes]
**Required Changes**: [List of required changes]
**Next Steps**: [What needs to happen next]
Input: Review specification for user dashboard
Output:
## Quality Gate: Specification Gate
### Gate Type
Specification
### Work Reviewed
specification-user-dashboard.md
### Quality Criteria
#### Criterion 1: All requirements documented
- **Status**: Met
- **Notes**: All functional and non-functional requirements are documented
#### Criterion 2: Technical approach defined
- **Status**: Met
- **Notes**: Technology stack, architecture, and implementation approach are clearly defined
#### Criterion 3: Dependencies identified
- **Status**: Met
- **Notes**: Dependencies on authentication, database, and API are identified
#### Criterion 4: Acceptance criteria clear
- **Status**: Met
- **Notes**: Clear acceptance criteria for each requirement
#### Criterion 5: No ambiguous requirements
- **Status**: Met
- **Notes**: All requirements are clear and unambiguous
### Overall Assessment
**Status**: Approved
### Issues Found
None
### Feedback
Specification is complete and ready for task breakdown. All criteria are met.
### Decision
**Can Proceed**: Yes
**Required Changes**: None
**Next Steps**: Proceed to scrum-master for task breakdown
Input: Review design specifications for login page
Output:
## Quality Gate: Design Gate
### Gate Type
Design
### Work Reviewed
Design specifications for login page (TASK-010-DESIGN)
### Quality Criteria
#### Criterion 1: Design specs complete
- **Status**: Met
- **Notes**: Layout, components, colors, and typography are specified
#### Criterion 2: Accessibility requirements met
- **Status**: Partial
- **Notes**: Most accessibility requirements met, but missing focus indicators specification
#### Criterion 3: Responsive design specified
- **Status**: Met
- **Notes**: Breakpoints and responsive behavior are defined
#### Criterion 4: Design tokens defined
- **Status**: Met
- **Notes**: Colors, spacing, and typography tokens are defined
#### Criterion 5: Implementation-ready
- **Status**: Partial
- **Notes**: Mostly ready, but missing focus indicator specs needed for implementation
### Overall Assessment
**Status**: Changes Requested
### Issues Found
- **Missing Focus Indicators**: Design specs don't specify focus indicator styles for form inputs and buttons. This is required for accessibility and implementation.
### Feedback
Design is mostly complete but needs focus indicator specifications added. Once added, design will be ready for implementation.
### Decision
**Can Proceed**: After Changes
**Required Changes**:
- Add focus indicator specifications for form inputs
- Add focus indicator specifications for buttons
- Ensure focus indicators meet WCAG contrast requirements
**Next Steps**: Update design specs with focus indicators, then re-review
Input: Review implementation of user authentication
Output:
## Quality Gate: Implementation Gate
### Gate Type
Implementation
### Work Reviewed
User authentication implementation (TASK-015)
### Quality Criteria
#### Criterion 1: Code implements requirements
- **Status**: Met
- **Notes**: Code implements login and registration as specified
#### Criterion 2: Unit tests written and passing
- **Status**: Not Met
- **Notes**: Unit tests are written but 3 tests are failing
#### Criterion 3: Integration tests passing
- **Status**: Not Met
- **Notes**: Integration tests not written
#### Criterion 4: Code follows style guide
- **Status**: Met
- **Notes**: Code follows project style guide
#### Criterion 5: Documentation complete
- **Status**: Partial
- **Notes**: Code comments present but API documentation is missing
### Overall Assessment
**Status**: Blocked
### Issues Found
- **Failing Tests**: 3 unit tests are failing, indicating bugs in implementation
- **Missing Integration Tests**: Integration tests are required but not written
- **Missing API Documentation**: API documentation is required but missing
### Feedback
Implementation has several quality issues that must be resolved before proceeding:
1. Fix failing unit tests
2. Write and pass integration tests
3. Add API documentation
### Decision
**Can Proceed**: No
**Required Changes**:
1. Fix failing unit tests (identify and fix bugs)
2. Write integration tests for authentication flow
3. Add API documentation for authentication endpoints
**Next Steps**: Fix issues and resubmit for gate review
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.