This skill should be used for periodic review of all Claude Code skills. Triggers include "audit my skills", "which skills need work", "skill inventory", or when starting a skill improvement session. Identifies staleness, gaps, redundancy, and prioritizes improvements.
Your approach to handling standards summary. Use this skill when working on files where standards summary comes into play.
Skill for ensuring visual consistency and preventing layout shifts during responsive transitions.
앱 개발 워크플로우를 시작합니다. 요구사항 분석(prd.md) -> 작업 계획(todo.md) -> Agent 분담 실행 -> 코드 리뷰 -> 최종 테스트 순서로 체계적인 앱 개발을 진행합니다. "/app-dev-workflow", "앱 개발 워크플로우", "앱 워크플로우로" 등의 명령으로 활성화됩니다.
並列エージェント派遣スキル。独立した問題に複数エージェントを同時割り当てする方法。
Work plan validation for completeness, clarity, and BOMvault compliance. Catches gaps and ambiguities before implementation begins.
Expert project management covering planning, execution, stakeholder management, risk mitigation, and delivery excellence.
When the user asks about roadmap planning, sprint planning, milestone estimation, or capacity planning
Store project-specific insights and context into file-based memory. Use after completing tasks that reveal important details about THIS codebase. Use when user says "--project-store" or "--learn" (you decide which scope, may use both) or after discovering project-specific patterns. Skip for universal patterns (use coder-memory-store) or routine work.
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
Project development workflow patterns including Plan-Build-Review-Fix cycle and feature development processes.
過去のセッションの進捗ファイルを参照して作業コンテキストを継続するためのガイド。(1) 新しいセッションを開始して以前の作業を継続したい時、(2) 過去に何をやったか思い出したい時、(3) 中断した作業の続きを始める時、(4) プロジェクトの進捗履歴を確認したい時
