Loading...
Loading...
Found 653 Skills
Co-author a Pantagruel (.pant) specification through guided conversation. Use when the user wants to write, design, or iterate on a Pantagruel spec file. Helps users think rigorously about domains, rules, invariants, actions, and initial state by asking clarifying questions rather than guessing. Trigger when user mentions writing a spec, modeling a system, or working with .pant files.
Verifies implementation against specifications by checking requirement fulfillment, task completion, and contract implementation. Generates a fulfillment report with coverage metrics. Always run after /speckit.implement completes.
Create Test Specifications (TSPEC) - Layer 10 artifact for unit, integration, smoke, and functional test cases
Automated fix skill that reads review reports and applies fixes to SPEC (Specification) documents - handles broken links, YAML structure issues, missing files, and iterative improvement
Automated fix skill that reads review reports and applies fixes to TSPEC (Test Specification) documents - handles broken links, element IDs, test case structure issues, and iterative improvement
Automated TSPEC generation from SPEC - generates test specifications for UTEST, ITEST, STEST, FTEST with TASKS-Ready scoring
Automatically generate mobile-first responsive CSS/SCSS when creating component styles or mentioning responsive design. Implements standard breakpoints (768px, 1024px), ensures WCAG AA color contrast, creates touch-friendly interfaces (44px minimum targets), adds proper focus indicators, supports reduced motion, scales typography responsively, and provides detailed technical specifications with exact values.
Write, review, and validate commit messages following the Conventional Commits v1.0.0 specification. Use when: (1) crafting a git commit message for any change, (2) reviewing or correcting an existing commit message, (3) choosing the right commit type for a change, (4) deciding how to mark a breaking change, (5) writing multi-line commits with body and footers, or (6) understanding how commits map to SemVer bumps (PATCH/MINOR/MAJOR). Covers all standard types: feat, fix, docs, chore, refactor, perf, test, build, ci, style, revert.
Scaffold, status-check, and manage specification directories. Handles auto-incrementing IDs, README tracking, phase transitions, and decision logging in docs/specs/. Used by both specify and implement workflows.
Evaluate whether a development ticket (user story, feature request, bug report, etc.) is ready for development, and provide specific, actionable feedback if it is not. Use this skill whenever the user asks to triage, evaluate, assess, review, or check the readiness of a ticket, story, issue, or work item. The ticket can come from anywhere: pasted inline, read from a file, fetched from Jira or another tracker via MCP, or any other source. Also use this when a user asks "is this ticket ready?" or "what's wrong with this ticket?" or wants to improve a ticket's specification.
Validate Technical Specifications (SPEC) documents against Layer 9 schema standards
Validate Test Specification (TSPEC) documents against Layer 10 schema standards