plan-complete
Complete a plan by updating design docs and removing the transitory plan file. Use when implementation is finished and knowledge should be persisted to design documentation.
Complete a plan by updating design docs and removing the transitory plan file. Use when implementation is finished and knowledge should be persisted to design documentation.
Gestion de projet pour agence Web - du brief à la livraison. Utilise ce skill quand: (1) planification d'un projet web, (2) estimation et chiffrage, (3) suivi d'avancement, (4) communication client, (5) gestion des risques projet, (6) coordination des équipes, (7) livraison et recette.
Periodic review of all 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.
Execute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1, fn-1.2).
SKILL.md의 모든 표준(문서화, 리스크 평가, 롤백 전략, 엄격한 TDD)을 준수하는 고급 기능 구현 워크플로우입니다.
Use when executing implementation plans with independent tasks in the current session
Deep analysis of ticket urgency and impact to determine accurate priority level
Agent development workflow and discipline skills. Use when developing features, debugging issues, managing code branches, writing plans, or ensuring code quality through TDD and systematic processes. Triggers on any software development task that benefits from structured workflows.
Crear y mantener procedimientos como skills (SKILL.md) con objetivo, cuando usar, pasos y checklist.
Fetch tasks from Linear backlog and handle user selection. Saves selected task context for use in feature/bug/plan workflows. Reduces context usage by consolidating Linear API interactions.
[DEPRECATED] This skill is no longer used. Feature tracking has migrated to PROJECT.md.
Use when translating a program/app idea into a VibeDev MCP Job (deliverables, definition of done, invariants, and a small step plan) and preparing it to transition to READY without implementing features yet
Incident postmortem methodology and templates. Use when conducting incident postmortems, writing postmortem reports, establishing postmortem processes, or performing post-incident analysis.
Creates a WorkPlan (Schedule of Intent) and logs U.Work.
docs/plan.md内のTODOリストを管理します。TODO項目の追加、完了マーク、整理を行います。 ユーザーがplan.mdの更新、TODO管理、計画の進捗確認を依頼したときに使用してください。 プロジェクト固有のTODO形式ルール(フラット構造、エピック化など)を遵守します。
Complete story implementation workflow from start to finish. Use when implementing user stories, features, or epics. Handles validation, development (with optional parallel execution), QA review, issue resolution, and PR creation. Can implement single stories, multiple stories, or entire epics in parallel.
Start working on a tracked issue. Use when beginning work on an issue, logging progress, or managing issue workflow.
Standard 5-phase workflow for most development tasks - bugs, small features, refactors (30-60 min)
This skill should be used when the user asks to "collect GitHub activity", "generate GitHub report", "show my PRs and commits", "what did I work on in GitHub", or requests activity summaries from GitHub for specific date ranges. Provides workflow for collecting issues, PRs, and commits via GitHub CLI.
Structured peer review for analytical work. Use when reviewing teammates' analysis, providing constructive feedback, or establishing analysis quality standards.
Use when you have a written implementation plan to execute with review checkpoints
進捗報告書を作成するスキル。開発案件の進捗状況を、技術的背景を持たないステークホルダーにもわかりやすく伝える報告書を生成。「進捗報告を作って」「ステータスレポートを書いて」「報告書を作成して」などのリクエストに使用。
Scans and reports all planning-related components across marketplace bundles