prism-devtools

Slash commands for activating PRISM personas and workflows.

Activate PRISM Software Architect persona

Cancel the active PRISM workflow

Activate PRISM Full Stack Developer persona

Activate PRISM Product Owner persona

Approve PRISM workflow gate and advance

Launch the live PRISM workflow dashboard (TUI)

Start the PRISM TDD workflow loop

Reject at red_gate and loop back to planning

Check current PRISM workflow state

Activate PRISM QA Engineer persona

Activate PRISM Scrum Master persona

Activate PRISM Support persona

Validate the PRISM dashboard TUI renders correctly via headless test

Verify story follows established architecture patterns and respects system boundaries. Use after epic alignment.

Verify story aligns with parent epic requirements and doesn't have scope creep. Use after content validation.

Analyze epic and suggest story decomposition with dependencies and sizing. Use before creating stories from epic.

Verify story File List section matches actual git changes. Use before marking story ready for review.

Validate Markdown references in Claude instructions to find broken links. Use at session start or before documentation changes.

Verify code meets linting and formatting standards. Use during development to catch quality issues early.

Scan PRISM and skill files for hardcoded paths that break portability across machines and users. Use before commits or when onboarding new team members.

Create/update QA gate YAML files with status decision. Use at end of QA review.

Trace PRD → Epic → Story → Code → Tests for complete requirements coverage. Use during QA review.

Validate story content quality (acceptance criteria measurable, tasks sized, etc.). Use after structure validation passes.

Validate story file structure matches PRISM template. Use immediately after story creation.

Scan PRISM instructions for terminology confusion between skills, agents, and tasks. Use before documentation changes or when instructions cause Claude to misinterpret invocation methods.

Execute test suites and report results. Use before marking story complete or after implementing fixes.

Create custom Claude Code sub-agents with specialized expertise and tool access. Use when you need to build reusable agents for specific tasks like code review, debugging, data analysis, or domain-specific workflows.

Use when Dev agent needs to implement fixes based on QA gate results. Reads QA outputs, creates prioritized fix plans, and applies code/test changes to address identified issues.

Create and manage project-level skills shared via git. Skills with prism: metadata are auto-discovered and injected into every PRISM workflow step. Use when teams need project-specific skills available to all agents throughout the workflow.

Use to improve story sizing accuracy by analyzing historical estimation data. Identifies patterns, updates size definitions, and refines PROBE proxy selections.

Use when handling sprint changes or scope adjustments. Analyzes change impacts, re-estimates affected stories, and adjusts sprint capacity using PRISM principles.

Use to generate development task documents for the Dev agent. Creates specifications describing WHAT needs fixing based on validated issues and investigations.

Use when creating new Epic documents. Groups related user stories, includes risk analysis, integration points, and story breakdown with PROBE estimation.

Use to create failing tests before implementing features (TDD approach). Ensures test-first development workflow.

Use to identify and prepare the next logical story based on project progress. Creates comprehensive story files with full technical context.

Use to create QA task documents. Generates test specifications and validation requirements for QA team.

Use to decompose user stories into individual development tasks. Creates task documents that can be assigned, estimated, and tracked.

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

Use to systematically validate documents, stories, or processes against defined checklists. Ensures quality and completeness.

Use when user mentions a Jira issue key (e.g., PLAT-123) or needs context from Jira. Retrieves and formats issue details for PRISM agent workflows.

File-first architecture principle for understanding codebases. Agents should read source files directly instead of relying on summaries, RAG, or pre-loaded context. Use Glob/Grep/Read tools.

Manage Claude Code hooks for workflow automation. Create, configure, test, and debug hooks that execute at various lifecycle points. Supports all hook events (PreToolUse, PostToolUse, SessionStart, etc.) with examples and best practices.

Initialize PRISM .context folder in current project. Use when starting PRISM work in a new project or setting up context management.

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

[DEPRECATED] PRISM-Memory has been archived. This skill is no longer active.

Use for root cause analysis of bugs or issues. Systematically investigates problems to identify underlying causes.

Jira integration for issue search, context fetching, and story planning with templates. Use when: user mentions issue keys (PLAT-123, JIRA-456), asks to "search backlog", "find stories", "look for bugs", needs "ticket details", wants to "plan a story", "create a story", "write a story", "user story for", mentions "jira template", "story template", or asks about acceptance criteria.

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

Start PRISM TDD workflow loop using Ralph Wiggum pattern. Auto-progresses through Planning, TDD RED (failing tests), TDD GREEN (implementation), and Review phases. Use when user wants to run the core development cycle.

Use to apply PROBE (PROxy-Based Estimation) method for story sizing. Uses historical data for accurate effort estimation.

Use to create or update quality gate decision files for stories. Provides clear pass/fail decisions with actionable feedback.

Use when a story needs to be resized based on new information. Adjusts estimates and splits/combines stories as needed.

Use to perform comprehensive test architecture review with quality gate decision. Creates both story updates and detailed gate files.

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.

Shared reference documentation for PRISM skills. Contains common best practices, command patterns, and examples used across multiple skills.

Build efficient, scalable Claude Code skills using progressive disclosure and token optimization. Use when creating new skills, optimizing existing skills, or learning skill development patterns. Provides templates, checklists, and working examples.

Use to break down large stories into optimally-sized stories (1-3 days). Applies PSP measurement discipline.

Use as reference guide for strangler pattern implementation. Provides patterns and best practices for legacy migrations.

Use when implementing strangler pattern for legacy migrations. Safely migrates controllers with feature flag control.

Use to design test strategies and create test specifications. Documents testing approaches for stories.

Use to trace requirements through implementation. Maps acceptance criteria to code and tests.

Run all PRISM documentation quality checks (docs, links, portability). Use before committing to .prism, or to check if anything is broken. Invoked by "validate all", "run all checks", "check prism", or "/validate-all".

Use to validate reported issues. Confirms reproducibility and documents validation evidence.

Validate markdown file references in .claude and .prism directories. Use to find broken links before committing documentation changes.

6 hooks across 3 events