Shinpr@Claude Code Workflows

Create work plan from design document and obtain plan approval

Execute tasks following appropriate rules with rule-advisor metacognition

Execute materialized task files in autonomous execution mode

Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval

Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved corrections.

Selects the smallest set of task-execution skills and metacognitive safeguards for standalone task and diagnosis workflows.

Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.

Investigate problem, verify findings, and derive solutions

Orchestrate the complete implementation lifecycle from requirements to deployment

React/TypeScript frontend development rules including type safety, component design, state management, and error handling. Use when implementing React components, TypeScript code, or frontend features.

Language-agnostic coding principles for maintainability, readability, and quality. Use when implementing features, refactoring code, or reviewing code quality.

Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.

Create frontend work plan from design document and obtain plan approval

Update existing design documents (Design Doc / PRD / ADR) with review

Execute materialized frontend task files in autonomous execution mode

Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.

Adjust an already-implemented UI in-session with verification against the design source

Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval

Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.

Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.

Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream consumers can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.

Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.

Execute materialized fullstack task files with layer-aware agent routing

Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Use when asked to create or update a repository quality profile.

Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.

Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.

Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review workflow

Separates the outcome a change must produce from the requirements proposed to reach it, records what the user excluded, and bands cost from structure. Use when a requirement enters a workflow, before design begins.

Records where resources outside the repository live (design source, design system, API schema, IaC source, secret store) and how design, implementation, and verification reach them. Use when work depends on an external resource, or when the user mentions design source, design system, API schema, IaC source, secret store, or canonical source.

Orchestrate full-cycle implementation across backend and frontend layers

Add integration/E2E tests to existing codebase using Design Docs

Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.