Learn and extract writing style patterns from exemplar text for consistent application. Use when creating a style guide from existing content, ensuring consistency across documents, learning a specific author's voice, customizing AI output style. Do not use when detecting AI slop - use slop-detector instead. just need to clean up existing content - use doc-generator with --remediate. Use this skill to build style profiles from exemplar text.

Use this skill BEFORE building complex tool chains. Optimize proactively. location: plugin token_budget: 200. Use when >3 tools chained sequentially, large datasets (>10k rows), large files (>50KB), context usage >25%. Do not use when simple tool calls that do not chain. DO NOT use when: context pressure is low and tools are fast.

Browse the rule catalog and guide installation. Use when looking for ready-made rules, installing standard rules, browsing available categories. Do not use when writing custom rules - use writing-rules skill instead.

Detect and flag AI-generated content markers in documentation and prose. Use when reviewing documentation for AI markers, cleaning up LLM-generated content, or auditing prose quality. Do not use when generating new content (use doc-generator) or learning writing styles (use style-learner).

Configure GitHub Actions CI/CD workflows for automated testing, linting, and deployment. Use for CI/CD setup and quality automation. Skip if CI/CD configured or using different platform.

Provides structural context for downstream review and refactoring workflows. Use when before architecture reviews to understand file organization, exploring unfamiliar codebases to map structure, estimating scope for refactoring or migration. Do not use when general code exploration - use the Explore agent. DO NOT use when: searching for specific patterns - use Grep directly.

Quota tracking, threshold monitoring, and graceful degradation for rate-limited API services. quota, rate limiting, usage limits, thresholds.

Run git-workspace-review first to capture repo context. Use when README requires structural refresh, adding features to documentation, aligning readme with exemplar standards, improving project presentation. Do not use when updating inline docs - use doc-updates. DO NOT use when: consolidating ephemeral reports - use doc-consolidation.

Analyze individual skill complexity and get modularization recommendations. For ecosystem-wide evaluation, use /skills-eval instead.

Create markdown-based behavioral rules preventing unwanted actions. create hookify rule, behavioral rule, prevent behavior, block command Use when: preventing dangerous commands, blocking debug commits, enforcing conventions DO NOT use when: hook scope (abstract:hook-scope-guide), SDK hooks (abstract:hook-authoring), evaluating hooks (abstract:hooks-eval).

Create clear, testable specifications with user stories and acceptance criteria. spec writing, feature specification, requirements, user stories Use when: creating new specifications or writing acceptance criteria DO NOT use when: converting specs to tasks - use task-planning.

Use this skill BEFORE resource-intensive operations. Establish baselines proactively. location: plugin token_budget: 400. Use when session starts (auto-load with token-conservation), planning builds or training that could pin CPUs/GPUs for >1 minute, retrying failed resource-heavy commands. Do not use when simple operations with no resource impact. DO NOT use when: quick single-file operations.

automatically create GitHub issues for workflow improvements via /fix-workflow. Use when workflows fail, timeout, or show inefficient patterns. Do not use when normal workflow execution, simple command errors.

Configure three-layer pre-commit system with linting, type checking, and testing hooks. Use for quality gate setup and code standards. Skip if pre-commit is optimally configured.

Generate phased, dependency-ordered tasks from specs. Identifies parallelization opportunities. task planning, dependency ordering, phased breakdown, parallel tasks Use when: converting specifications to implementation tasks DO NOT use when: writing specs - use spec-writing. Not for execution - use speckit-implement.

TDD-style testing methodology for skills using fresh subagent instances to prevent priming bias and validate skill effectiveness. Use when validating skill improvements, testing skill effectiveness, preventing priming bias, measuring skill impact on behavior. Do not use when implementing skills (use skill-authoring instead), creating hooks (use hook-authoring instead).

Architect skills as modular blocks to control token usage and complexity. Use when creating skills >150 lines, breaking down monolithic skills, or planning new architecture. Do not use for evaluating existing skills (use skills-eval) or writing human-facing prose (use writing-clearly-and-concisely). Check this skill before starting any new skill development.

Consult this skill when formatting final review deliverables. Use when formatting final review outputs, ensuring consistent deliverable structure, making findings comparable across reviews. Do not use when capturing evidence during analysis - use proof-of-work. DO NOT use when: reviewing changes - use diff-analysis or review-core first.

Transform specifications into implementation plans with architecture design and dependency-ordered tasks. Use for spec-to-plan conversion, task breakdown, effort estimation. Skip if no spec exists.

balancing accuracy with token efficiency.