Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Verify and close stories after frontend/backend tasks are completed. Check ALL related task files, update story acceptance criteria checkboxes. UNIQUE VALUE: Ensures BOTH frontend AND backend tasks are verifie...
convert structure outline into a detailed implementation plan
Fixes tasks in To Rework and returns them to To Review. Applies reviewer feedback only for the selected task.
Diagnoses GitHub Actions CI/CD failures for FanHub's Node.js workflows. Identifies test failures, build errors, Docker issues, and environment problems.
Transform requirements into well-structured User Stories using "As a [user], I want [goal], So that [benefit]" format with Given/When/Then acceptance criteria. Use this skill when: - User asks to "write user s...
Create comprehensive Product Requirements Documents (PRD) that define what to build and why, focusing on goals, scope, user stories, and success criteria without implementation details. Use this skill when: -...
first step of planning
分析 GitHub Issue，判断类型和严重程度，定位 Bug 根因，自动修复简单问题。当 Issue 被创建或需要分析问题时使用。
Audit project documentation quality across 6 categories (Hierarchy, SSOT, Compactness, Requirements, Actuality, Legacy). Use when documentation needs quality review, after major doc updates, or as part of ln-10...
Product Owner skill for managing product backlogs, user stories, roadmaps, requirements gathering, and stakeholder communication. Use when working with product strategy, feature prioritization, sprint planning,...
Review logs from ~/logs and remote log APIs to provide orientation and context for the day. Use when starting a work session, checking what happened recently, or needing context on recent activity. Reads daily...
Executes implementation tasks (Todo -> In Progress -> To Review). Follows KISS/YAGNI, guides, quality checks. Not for test tasks.
Work on projects through well-defined specs. Spec-first approach with no ambiguity.
Brainstorming techniques for idea generation. Use when facilitating brainstorming sessions, leading ideation exercises, or helping teams generate creative solutions.
Design a detailed technical document for a single system, including architecture diagrams, interface design, data models, and trade-off analysis.
Write PRDs documenting what users need and why. Use when writing PRDs or product requirements.
暗黙知抽出Skill。仕様策定（/spec）の前段階として、ユーザーの暗黙知を対話的に引き出す。定義の明確化、トレードオフの掘り下げ、技術的制約の確認を段階的に実施。Use when "要件を整理して", "暗黙知を言語化して", "仕様...
UX 사용자 흐름 다이어그램 설계. Use when (1) UI가 있는 프로젝트 기획, (2) 사용자 여정 맵 작성, (3) 화면 플로우 설계.
This sop guides you through the process of transforming a rough idea into a detailed design document with an implementation plan and todo list. It follows the Prompt-Driven Development methodology to systematic...
Design thinking methodology for human-centered problem solving. Use when facilitating design thinking workshops, user research sessions, or creative problem-solving activities.
Guide to polishing the User Interface (Display Names, Ordering, Visibility).
Define what you want to build (requirements and user stories) - focus on WHAT and WHY, not the tech stack
Extract domain concepts from vague user requirements—entities, flows, and “dark matter” (what users don’t say). Based on Domain-Driven Design (DDD).
プロセス担当エージェント「iFlow」を起動します。中級者のプロセス・ワークフローエージェントとして、プロセス設計・CI/CD・タスク振り分けを担当します。
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.