ai_tools

Use when asked for a codebase scorecard, quality audit, 9-dimension assessment, post-merge/refactor/release health review, or due-diligence review.

Guide a product owner through defining a feature — UI, backend, or full-stack. Conducts a structured interview that branches based on feature type, then produces a structured Feature document. Use when a PO wants to define a new feature, plan a screen flow, document an API, or describe a backend capability. Examples: "let's define a new feature", "I want to plan a UI flow", "help me define an API feature", "plan a backend service", "/feature-writer".

Break a Feature into individual stories — one per user action, CRUD operation, or backend operation — and create each one interactively using the story-writer skill. Use after /feature-writer, or when given a Feature to decompose. Supports UI, backend, and full-stack features. Supports Jira and Azure DevOps. Examples: "break this feature into stories", "split this feature into stories", "/story-splitter".

Use when asked to evaluate, review, or score a story or bug for quality, readiness, or completeness - especially when a product owner wants feedback before refinement or sprint planning. Supports Jira, Azure DevOps, or pasted content.

Use when a product manager or product owner wants to create a new story, bug, or task - guides them interactively through writing quality issues with proper acceptance criteria and technical details. Supports Jira and Azure DevOps.

Use this skill when performing a security review of a codebase, app, or system design. Triggers include pre-launch security checks, post-incident audits, reviewing auth/authz systems, evaluating third-party integrations, or any request for adversarial threat modeling.

Systematically analyze bugs, failures, or unexpected behavior to identify root causes. Examines code, data, dependencies, and logs without proposing fixes, producing a structured analysis that surfaces assumptions, evidence, gaps, and the simplest path forward.

Generate an AI-optimized YAML code map (.codemap.yaml) at the repository root. The map captures project structure, API surface, services, models, relationships, and conventions so that AI agents can quickly navigate and understand the codebase without cold-start exploration. Invoke this skill to create or regenerate the map.