katachi

Plugin katachi from marketplace asermax-plugins in asermax/claude-plugins. Commands read from the repo's manifest — 5 days ago.

Skills (32)

• add-delta

  Add a new delta on-the-go without full upfront planning

• analyze-impact

  Analyze the impact of a proposed change on features and dependencies

• analyze

  Review project state, find gaps, assess change impact

• commit

  Analyze uncommitted changes and create grouped conventional commits

• decision

  Document an architecture or design decision

• delta-details

  Show comprehensive details for a specific delta or answer a question about it

• delta-summary

  Display a summary table of available deltas or show recommended next deltas

• deltas

  Extract deltas from the project vision

• design-delta

  Write design rationale for a delta

• eject

  Eject katachi plugin into self-contained project structure

• framework-core

  Load when working with any katachi framework command. Provides workflow principles, status tracking conventions, and decision guidance. This skill establishes the collaborative context for all framework operations.

• implement-delta

  Implement a delta following its plan

• init-framework

  Initialize the katachi framework directory structure

• iterative-development

  Load when adding deltas or analyzing impact on existing framework. Supports progressive development without requiring everything upfront. Used by /add-delta and /analyze-impact commands.

• land-delta

  Prepare a reconciled delta branch for merging into main. Rebases the delta branch onto main, reconciles code and documentation with changes introduced on main, and validates conflicting areas with reviewer agents.

• migrate-to-deltas

  Migrate existing katachi project to delta-based workflow

• optimize-docs

  Analyze docs for optimization opportunities (split, simplify, remove)

• patch

  Apply a focused change using a compressed delta workflow. Reads project context (specs, designs, decisions), plans inline via plan mode, implements, and reconciles feature documentation in a single session without creating intermediate delta files.

• plan-delta

  Create step-by-step implementation plan for a delta

• reconcile-delta

  Reconcile delta implementation into feature documentation

• research-docs

  Use BEFORE designing, implementing, planning, or configuring ANY feature involving libraries, frameworks, or complex APIs - even before reading existing code. Fetches current documentation to ensure correct usage. Triggers on third-party libraries (such as react-query, FastAPI, Django, pytest), comp

• retrofit-decision

  Document an existing decision from code as an ADR or DES

• retrofit-design

  Create design documentation from existing implementation

• retrofit-existing

  Load when retrofitting framework documentation to existing code. Supports creating specs and decisions from implementations, enabling gradual framework adoption for existing projects.

• retrofit-project

  Full project retrofit - discover modules, create specs, designs, decisions, and vision from existing code. Use when initializing the katachi framework on an existing project with code, or when the user wants to retrofit documentation for the entire project at once.

• retrofit-spec

  Create a feature specification from existing code

• review-code

  Review code against specs, designs, and decision compliance

• review-delta

  Review a delta's implemented code against specs, designs, and decisions

• review-priorities

  Conversational session to review and assign delta priorities

• spec-delta

  Write a specification for a delta

• vision

  Create or update the project vision document

• working-on-delta

  Load when executing spec/design/plan/implement commands for a specific delta. Provides templates, agent dispatch patterns, and workflow orchestration for per-delta work.

Subagents (13)

• code-reviewer

  Review implemented code against specs, designs, and project decisions. Use this agent after implementing a delta to validate compliance before committing.

• codebase-analyzer

  Analyze existing code to infer requirements and decisions for retrofitting documentation. Use this agent when creating specs or decisions from existing implementations.

• decision-reviewer

  Review decision classifications and promotions. Use this agent to validate whether decisions should become ADRs or DES patterns, and whether existing decisions need updates.

• delta-validator

  Validate delta definitions for atomicity, clarity, and naming quality. Use this agent to review deltas before adding them to DELTAS.md.

• design-reviewer

  Review delta designs for coherence, pattern alignment, and completeness. Use this agent after drafting a design to validate it before creating an implementation plan.

• doc-optimizer

  Analyze documentation for optimization opportunities including splitting long documents, reducing verbosity, and identifying obsolete/redundant documents.

• doc-researcher

  INTERNAL AGENT - Do not call directly. This agent is invoked exclusively by the katachi:research-docs skill. The skill handles when to search documentation and how to structure the search parameters with library name and topic.

• impact-analyzer

  Analyze the impact of proposed changes on existing features and dependencies. Use this agent when adding deltas or making changes to understand ripple effects on feature documentation.

• optimization-validator

  Validate that document optimizations preserve intent and content - no data loss. Use this agent after executing document optimizations to ensure nothing was lost.

• plan-reviewer

  Review implementation plans for completeness and feasibility. Use this agent after drafting a plan to validate it before implementation begins.

• priority-reviewer

  Validate priority assignments for consistency and alignment with project goals. Use this agent to review priorities before applying batch updates.

• spec-reviewer

  Review delta specifications for completeness, testability, and clarity. Use this agent after drafting a spec to validate it before proceeding to design.

• spike-runner

  Investigate flagged unknowns in shape parts. Researches questions about mechanisms where the HOW is not yet understood, and identifies potential requirement implications.