ai-tools

Plugin ai-tools from marketplace ai-tools in sean-m-cooper/ai_tools. Commands read from the repo's manifest — yesterday.

Skills (12)

• audit-writing-architecture

  Audit technical and professional nonfiction with SOLID, DRY, YAGNI, paragraph contracts, and refactoring practices. Use when asked to review an article, essay, white paper, newsletter, documentation set, or similar nonfiction for structural cohesion, coupling, reader context, replaceable support, re

• author-style-guide

  Analyze an author's real writing samples, interview them about observed patterns and intended positioning, and create or update a personalized style guide for articles, newsletters, social posts, email, product writing, or thought leadership. Use when an author wants to define their voice, extract a

• code-map

  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 cre

• cold-start-audit

  Audit a standalone artifact for context its intended reader, operator, or AI collaborator needs but was never given. Use when asked whether an article, essay, specification, architecture decision, proposal, user story, runbook, prompt, instruction file, or similar artifact can stand on its own; when

• content-voice-audit

  Run a read-only heuristic audit of Markdown blog posts, newsletters, essays, and thought-leadership content for formulaic cadence, weak evidence, generic significance, canned phrasing, repeated AI-pattern signals, and thin structure. Use when asked to run a content or slop audit, identify low-scorin

• content-voice-revision

  Revise selected blog posts, newsletters, and thought-leadership content using findings from a content audit. Use when asked to fix named essays, improve the lowest-scoring content, reduce AI-sounding cadence, add evidence or receipts, or strengthen an argument without changing the author's voice. Wo

• feature-writer

  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 cap

• root-cause

  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.

• security-audit

  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.

• story-prefinement

  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.

• story-splitter

  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 Azur

• story-writer

  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.

Slash commands (1)

• /ai-tools:root-cause

Similar plugins