القائمة
Authoritative source for all validation, code review, and quality assurance workflows. Provides consistent quality gates across all development phases.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Query and manage project state and drive shark workflows — epics, features, tasks, bugs, change-cards, ideas. Use for ALL project state queries, task lifecycle, status transitions (status set / advance --outcome), claim/release/heartbeat leases, blocking/unblocking, notes/context/related-docs, status dashboards, analytics, creating/updating/deleting entities, and any command starting with "shark". Also the router for `/shark <verb>` and triggers the dispatch loop on `/run <key>`.
Multi-angle parallel code review. Six specialist subagents run in parallel (A: line-by-line bugs + production caller chains, B: removed behavior + SOLID, C: cross-file contracts + structural sibling check, D: reuse/complexity/idioms, E: tests design + counter-factual, F: standards crosswalk with citations), then a consolidator verifies and ranks findings into a PASS / PASS-with-triage / FAIL report with Blocker / Non-blocker / Nit triage. Triggered by /deep-review (aliases: /comprehensive-review, /pr-review). Flags: --fix (apply one-liner safe fixes), --comment (post as inline GitHub PR comments). Prompts live in references/angle-*.md and references/consolidator.md — readable on any platform even without the Workflow tool.
Write the test first, watch it fail, write minimal code to pass (user) - when implementing any feature or bugfix, before writing implementation code
Orchestrate User Acceptance Testing for a feature — gather evidence, run Codex as the sole assessor, present a no-opinion report to the user, record results, route rejections, and triage non-blocking findings.
Quick-capture and classify a work item discovered during development, routing it to the correct entity type (task, feature, bug, tech-debt, change-card, idea, or note) under the right parent. Searches existing entities first to avoid duplication, proposes a classification, and confirms before creating. Use when you encounter work that needs to be recorded for later, the user says "/triage", or something should be tracked but its home is unclear. This is a capture-and-classify tool, NOT a create-and-elaborate tool.
Authoritative source for all specification document generation workflows (Epics, Feature PRDs, Tasks). Provides standardized templates, procedures, and naming conventions for consistent documentation across all projects.
| name | quality |
| description | Authoritative source for all validation, code review, and quality assurance workflows. Provides consistent quality gates across all development phases. |
| version | 1.0.0 |
| created | "2025-12-09T00:00:00.000Z" |
| inputs | [{"entity_type":"the type of entity being validated (task|feature|epic|design|code)"},{"entity_key":"the entity key being validated"},{"spec_path":"absolute path to the specification document"},{"implementation_paths":"list of paths to implemented code or documentation"},{"test_paths":"list of paths to test files (optional)"},{"design_refs":"list of paths to design documents or wireframes (optional)"},{"acceptance_criteria":"list of acceptance criteria text to validate against"}] |
| outputs | [{"selected_workflow":"one of {validate-design, validate-tasks, review-code, test-planning, qa-testing, generate-standards}"},{"validation_report":"structured validation results (PASS|FAIL)"},{"issues_found":"list of {severity, description, location, remediation}"},{"coverage_analysis":"validation coverage and gaps"},{"recommendations":"actionable recommendations for improvement"}] |
This skill provides quality assurance capabilities with standardized validation and review workflows for maintaining high-quality deliverables throughout the development lifecycle.
Based on what needs validation, invoke the appropriate workflow:
When: Validating feature design documentation before task generation
Invoke: workflows/validate-design.md
Output: Validation report for design documents
Use case: Ensure all required design docs exist and are complete
When: Validating tasks are complete and ready for implementation
Invoke: workflows/validate-tasks.md
Output: Task readiness report with dependency analysis
Use case: Verify tasks are properly structured and sequenced
When: Reviewing code implementation against requirements and standards
Invoke: workflows/review-code.md
Output: Comprehensive code review report
Use case: Assess code quality, PRD alignment, and engineering standards
When: Reviewing task specifications BEFORE development begins
Invoke: workflows/test-planning.md
Output: Spec drift analysis + concrete acceptance test cases
Use case: Compare task spec against feature PRD for drift, write test plan that becomes the developer's source of truth. This is the quality gate between planning and development.
When: Validating implementation after code review
Invoke: workflows/qa-testing.md
Output: QA test results and exploratory findings
Use case: Validate implementation against pre-written test plan and acceptance criteria
All workflows reference these quality criteria files:
context/design-validation-criteria.md - Design document requirementscontext/task-validation-criteria.md - Task completeness checkscontext/review-rubric.md - Code review standardscontext/quality-gates.md - General quality standardsCommands and agents reference this skill using:
## Your Process
1. Analyze what needs validation
2. Invoke quality skill: quality/workflows/validate-{type}.md
3. Apply criteria from quality/context/{criteria-name}.md
4. Generate validation report with actionable feedback
All validation activities must:
For detailed usage instructions, see README.md