.prism

Read source files directly with Glob/Grep/Read. No RAG, no vector databases, no pre-loaded summaries.

Shared reference documentation: PRISM best practices, command patterns, and cross-skill examples.

Create, configure, test, and debug Claude Code hooks for lifecycle automation across 9 event types.

Search project knowledge - code, docs, expertise, patterns

Persist patterns, conventions, decisions, or failures to Mulch expertise for cross-session memory.

Run PRISM quality checks - docs, links, and portability. Use before committing or when something looks broken.

Bump version, update CHANGELOG, and create git tag for prism-devtools releases. Use when: user says "bump version", "release", "tag release", "version bump", "cut a release", "what version", "update version", or needs to publish changes.

Create custom Claude Code sub-agents with specialized expertise, limited tools, and reusable prompts.

Apply code/test fixes from QA gate results: prioritized plan from gate YAML and assessments.

Prompt optimization - scores, analysis, variant generation

Handle sprint changes and scope adjustments: analyze impact, re-estimate stories, and adjust sprint capacity.

Generate a dev task document for the Dev agent based on validated issue and investigation results.

Create failing test specs for TDD: document reproduction steps and assertions for Dev/QA handoff.

Generate QA task spec from validated issue: scenarios, test data, and handoff package for QA agent.

Use to analyze and document any project codebase. Creates comprehensive reference documentation for AI-assisted development including architecture and patterns.

Validate documents, stories, or processes against defined checklists with pass/fail report.

Initialize PRISM .context folder in a new project with context modules and CLAUDE.md setup.

Use to create complete architecture documentation structure. Creates all required architecture documents from templates.

Systematically investigate bugs to find root cause via code analysis, git history, and error tracing.

Use to assess non-functional requirements (security, performance, reliability, maintainability) through E2E integration testing patterns.

Create/update QA gate YAML for a story: PASS/CONCERNS/FAIL/WAIVED decision with actionable issues.

Use to assess and document risk factors for stories or features. Creates risk profiles with mitigation strategies.

Use for SDLC phase transitions. Ensures proper handoff between development phases with documentation.

Build, optimize, and validate Claude Code skills using progressive disclosure and token efficiency.

Safely migrate legacy controllers using strangler pattern with feature flags

Design E2E integration test strategy for a story: scenarios, patterns, and test spec document.

Map acceptance criteria to E2E integration tests: build traceability matrix and identify coverage gaps.

Validate reported issues using Playwright: confirm reproducibility and document evidence for Dev team.