Fix and validate Mermaid diagrams using mermaid-cli (mmdc). Use when Claude needs to fix parsing errors in Mermaid diagrams, validate diagrams, or when encountering Mermaid syntax issues. This skill reads rules from .claude/rules/mermaid.md and updates it with newly discovered patterns.
Reference and maintain documentation of the project's technical stack including frameworks, languages, databases, testing tools, and third-party services. Use this skill when choosing technologies for implementation, adding new dependencies or libraries, setting up project infrastructure, configuring build tools and package managers, integrating third-party services (authentication, email, monitoring), selecting appropriate frameworks for features, ensuring consistency with existing technology choices, documenting technology decisions, reviewing technology compatibility, or onboarding team members to the tech stack. Apply this skill when making technology decisions, adding new tools or services, documenting the stack, or ensuring new code aligns with the project's established technical architecture.
Transform rough product ideas into atomic task queues. Use when starting a new project from a vague concept or feature request.
This skill should be used when implementing features with human-in-the-loop verification. It provides the core Unit Work methodology including checkpoint-based development, confidence assessment, memory integration with Hindsight, and verification strategies. Use this skill for planning features, executing with checkpoints, reviewing code, and compounding learnings.
Orchestrates the full crowdfunding workflow phase-by-phase, ensuring each Skill runs in sequence with proper handoffs and validation gates.
Enforce stage-by-stage implementation for multi-step task briefs. Use when acting as the implementor to deliver one stage at a time, pausing for explicit user confirmation before proceeding unless the user requests all stages at once.
Decomposes a decision-complete PRD into a clear, minimal set of user-meaningful features with explicit dependencies, producing a roadmap-ready structure without prioritization, scheduling, or implementation detail.
Conducts comprehensive requirements review including completeness validation, clarity assessment, consistency checking, testability evaluation, and standards compliance. Produces detailed review reports with findings, gaps, conflicts, and improvement recommendations. Use when reviewing requirements documents (BRD, SRS, user stories), validating acceptance criteria, assessing requirements quality, identifying gaps and conflicts, or ensuring standards compliance (IEEE 830, INVEST criteria). Trigger when users mention "review requirements", "validate requirements", "check requirements quality", "find requirement issues", or "assess BRD/SRS quality".
Use when generating full planning hierarchy - orchestrates roadmap, stories, epics, and tasks creation
過去のセッションの進捗ファイルを参照して作業コンテキストを継続するためのガイド。(1) 新しいセッションを開始して以前の作業を継続したい時、(2) 過去に何をやったか思い出したい時、(3) 中断した作業の続きを始める時、(4) プロジェクトの進捗履歴を確認したい時
Help leaders give effective feedback using Kim Scott's Radical Candor framework. Use this skill when asked to: draft feedback for team members, prepare for difficult conversations, review feedback for tone and effectiveness, coach on giving/receiving feedback, prepare 1:1 talking points, or help navigate challenging interpersonal situations at work. The skill helps balance caring personally while challenging directly.
작업 계획서를 기반으로 TDD 방식으로 구현을 진행합니다. "구현 시작해줘", "개발 진행해줘", "코드 작성해줘", "작업 시작" 등을 요청할 때 활성화됩니다.
A comprehensive framework for high-performance engineering management and task execution. It guides users through reducing ambiguity, defining "Done," choosing the optimal leadership positioning, and managing risks via implication-based communication.
Execute research experiments using TDD methodology. Pops plans from .claude/plans/research_tasks/, implements with smoke/unit/integration tests, and documents results to results.md. Use when: (1) executing the next experiment from the queue, (2) executing a specific plan by number, (3) running an ad-hoc research idea with TDD.
Core planning principles for Portfolio Buddy 2 development. Use when: planning any feature implementation, modification, or refactoring. Ensures code preservation, mobile/desktop optimization, and thorough requirement gathering.
Analyze code review findings and create execution plan. Decides parallel vs sequential fixing based on issue severity and independence. Returns structured task list with clear fixer instructions.
Comprehensive guide to delivery governance including quality gates, standards, compliance, and balancing governance with agility
Best practices for using Claude Code in team environments. Covers skill management, knowledge capture, version control, and collaborative workflows.
Creates an implementation plan for an existing GitHub issue and adds it as a comment. Takes a GitHub issue number. Use when the user wants to plan a ticket, plan an issue, or says "plan ticket X" or "how should we implement issue
General programming best practices applicable to all languages. Covers clean code, testing, refactoring, version control, and development workflows. Use when writing or reviewing code in any language.
TDD-based implementation workflow for feature development, bug fixes, and code changes. Use when: implementing features, fixing bugs, adding functionality, writing new code, or making any code changes. Triggers: "implement", "add feature", "fix bug", "build", "create", "develop", "write code", "TDD", "test-driven".
