team-shinchan

Plugin team-shinchan from marketplace team-shinchan in seokan-jeong/team-shinchan. Commands read from the repo's manifest — 1 month ago.

Skills (58)

• analytics
• analyze
• autopilot
• backend
• bigproject
• brainstorm
• budget
• debate
• deepsearch
• design-review
• devops
• doctor
• eval
• fierce-compete
• fierce-debate
• fierce-option-panel
• fierce-ralph
• fierce-review
• forget
• frontend
• help
• impact-analysis
• implement
• learn
• lint-harness
• manage-skills
• memories
• micro-execute
• ontology
• orchestrate
• plan
• ralph
• requirements
• research
• resume
• review
• session-summary
• setup-hud
• setup
• simplify
• skill-feedback
• start
• status
• systematic-debugging
• test-driven-development
• ultrawork
• verification-before-completion
• verify-agents
• verify-budget
• verify-consistency
• verify-implementation
• verify-memory
• verify-skills
• verify-workflow
• version
• vision
• work-log
• writing-skills

Slash commands (59)

• /team-shinchan:analytics

  Analyze work tracker events for observability insights

• /team-shinchan:analyze

  Deep analysis with Hiroshi(Oracle)

• /team-shinchan:autopilot

  Autonomous execution from idea to working code

• /team-shinchan:backend

  Backend development with Buriburi (API, database, server logic)

• /team-shinchan:bigproject

  Large-scale project orchestration with Himawari (Atlas)

• /team-shinchan:brainstorm

  Structured problem exploration before requirements (Problem Reframe, Alternatives, Recommendation)

• /team-shinchan:budget

  View and manage workflow turn budgets

• /team-shinchan:debate

  Expert agents debate to find optimal solutions

• /team-shinchan:deepsearch

  Deep codebase exploration with Shiro(Explorer)

• /team-shinchan:design-review

  Compare design (Figma URL or mockup image) against implementation to detect UI mismatches (colors, layout, typography)

• /team-shinchan:devops

  DevOps and infrastructure with Masao (CI/CD, Docker, cloud)

• /team-shinchan:doctor

  Plugin health diagnostics with Doctor

• /team-shinchan:eval

  View agent evaluations and detect regressions

• /team-shinchan:fierce-compete

  Deterministic competitive code tournament (Workflow tier) — best of N implementations

• /team-shinchan:fierce-debate

  Deterministic adversarial debate (Workflow tier) for high-stakes decisions

• /team-shinchan:fierce-option-panel

  Default-on interview option-quality panel (Workflow tier) — diverse generators, majority-vote consensus, cautious-confidence judge, top-K

• /team-shinchan:fierce-ralph

  Deterministic loop-until-done (Workflow tier) for high-stakes long-running tasks

• /team-shinchan:fierce-review

  Deterministic adversarial code review (Workflow tier) for high-stakes scope

• /team-shinchan:forget

  Delete specific memories

• /team-shinchan:frontend

  Frontend development with Aichan (UI, React, CSS, accessibility)

• /team-shinchan:help

  Guide for using Team-Shinchan plugin

• /team-shinchan:impact-analysis

  Analyze cascade impact of changing a component using the ontology dependency graph

• /team-shinchan:implement

  Quick code implementation with Bo (features, bug fixes, utilities)

• /team-shinchan:learn

  Add new learning to memory

• /team-shinchan:lint-harness

  Run plugin consistency checks (agent, structure, drift)

• /team-shinchan:manage-skills

  Analyze changed files and ensure verify-* skill coverage integrity

• /team-shinchan:memories

  View and manage learned memories

• /team-shinchan:micro-execute

  Micro-task execution with per-task two-stage review (spec compliance + code quality)

• /team-shinchan:ontology

  Query, manage, and visualize the project-level ontology

• /team-shinchan:orchestrate

  Explicitly invoke Shinnosuke to orchestrate through the integrated workflow

• /team-shinchan:plan

  Create systematic work plans with Nene(Planner)

• /team-shinchan:ralph

  Persistently loops until task is fully complete

• /team-shinchan:release

  Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release

• /team-shinchan:requirements

  Hidden requirements analysis with Misae (risks, edge cases, implicit needs)

• /team-shinchan:research

  Research and documentation with Masumi (Librarian)

• /team-shinchan:resume

  Resume an interrupted workflow from where it left off

• /team-shinchan:review

  Code review and verification with Action Kamen (correctness, security, quality)

• /team-shinchan:session-summary

  Generate session summary from Work Tracker logs

• /team-shinchan:setup-hud

  Configure Claude Code's statusLine to display the Team-Shinchan HUD

• /team-shinchan:setup

  First-time setup and health check for Team-Shinchan plugin

• /team-shinchan:simplify

  Review and simplify changed code for quality and reuse

• /team-shinchan:skill-feedback

  View accumulated skill feedback and improvement suggestions

• /team-shinchan:start

  Start a new task with the integrated workflow

• /team-shinchan:status

  Show current workflow status

• /team-shinchan:systematic-debugging

  4-phase systematic debugging with root-cause analysis

• /team-shinchan:test-driven-development
• /team-shinchan:ultrawork
• /team-shinchan:verification-before-completion
• /team-shinchan:verify-agents
• /team-shinchan:verify-budget
• /team-shinchan:verify-consistency
• /team-shinchan:verify-implementation
• /team-shinchan:verify-memory
• /team-shinchan:verify-skills
• /team-shinchan:verify-workflow
• /team-shinchan:version
• /team-shinchan:vision
• /team-shinchan:work-log
• /team-shinchan:writing-skills

Subagents (15)

• actionkamen

  Reviewer that verifies and approves all work. Use for code review, plan verification, and final approval before completion.

• aichan

  Frontend Specialist for UI/UX development. Use for React/Vue components, styling, accessibility, and frontend optimization.

• bo

  Execution PO that coordinates domain specialists and implements general coding tasks. Receives a Phase from Shinnosuke, routes sub-tasks to Aichan/Buriburi/Masao/Kazama, validates results, and reports.

• buriburi

  Backend Specialist for API and database development. Use for REST/GraphQL APIs, database design, server logic, and security.

• himawari

  Master Orchestrator for large-scale complex projects. Decomposes multi-phase, cross-domain work into a phase plan; the bigproject skill then runs each phase as its own full start workflow.

• hiroshi

  Senior Advisor (Oracle) providing strategic advice and debugging consultation. Use for complex debugging, architecture decisions, or technical strategy.

• kazama

  Autonomous Deep Worker for complex long-running tasks. Use for major refactoring, complex implementations, or deep debugging sessions.

• masao

  DevOps Specialist for infrastructure and deployment. Use for CI/CD, Docker, Kubernetes, cloud infrastructure, and monitoring.

• masumi

  Librarian for documentation and information search. Use for finding docs, API references, and researching external information.

• midori

  Stage debate moderator (Midori). Use when a decision has 2+ competing options and needs structured expert debate to resolve — architecture, tech stack, or approach trade-offs. Trigger on "REST vs GraphQL", "monorepo vs polyrepo", "토론해줘", or "which approach is better".

• misae

  Requirements Analyst that interviews users, collects requirements, and discovers hidden risks. Use for Stage 1 requirements gathering.

• nene

  Strategic Planner that creates comprehensive implementation plans (PROGRESS.md). Stage 2 only — requirements are handled by Misae.

• shinnosuke

  Main Orchestrator that coordinates all work and delegates to specialist agents. Use for complex tasks requiring multiple agents.

• shiro

  Fast Explorer for quick codebase navigation and search. Use when you need to find files, search code, or understand project structure quickly.

• ume

  Multimodal Analyst (Ume) via /team-shinchan:vision. Use when input includes an image, screenshot, UI mockup, diagram, or PDF that must be read or extracted — not for code-only tasks. Trigger on "analyze this mockup/screenshot", "이 이미지 분석", or "extract from this PDF".

MCP servers (1)

• shadcn

  runs: npx shadcn@latest mcp

Hooks (30)

• SubagentStart

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/write-tracker.sh" HOOK_EVENT=SubagentStart

• SubagentStop

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/write-tracker.sh" HOOK_EVENT=SubagentStop

• PreToolUse

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/prompt-injection-guard.sh

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/security-check.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/deny-check.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/agent-tool-guard.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/budget-guard.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/workflow-guard.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/transition-gate.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/scope-guard.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/transition-gate.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/scope-guard.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/delegation-guard.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/delegation-guard.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/layer-guard.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/commit-lint.sh"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/pre-push-gate.sh"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/write-tracker.sh" HOOK_EVENT=PostToolUse

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/write-tracker.sh" HOOK_EVENT=PostToolUse

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/write-tracker.sh" HOOK_EVENT=PostToolUse

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/comment-checker.sh"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/comment-checker.sh"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/write-tracker.sh" HOOK_EVENT=UserPromptSubmit

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/trace-init.sh"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/intent-gate.sh"

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/write-tracker.sh" HOOK_EVENT=Stop

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/session-wrap.sh"

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/write-tracker.sh" HOOK_EVENT=SessionStart

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/session-init.sh"

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/scripts/run.cjs" "${CLAUDE_PLUGIN_ROOT}/hooks/ontology-auto-build.sh"

Similar plugins