implement-ticket
Implement a Beads ticket with documentation grounding and correction workflow
Implement a Beads ticket with documentation grounding and correction workflow
Generate a Marp presentation from an intent's spec. Use when the user wants to create slides for an intent or asks to make a presentation.
実装計画を作成する際にtmp/配下にファイルを配置するようガイドします。docs/への不要なドキュメント生成を防ぎ、一時的な計画ファイルを適切に管理します。
Structure analysis approach before starting work. Use when receiving new analysis requests, breaking down complex questions into steps, or planning iterative analysis workflows.
1作業=1ディレクトリ(docs/<work_item>/)で、implementedplan.md と tasks.md を作る手順とテンプレ。
Divide pedidos grandes em micro-tarefas pequenas e sequenciais antes de escrever qualquer código.
Creates structured Linear issues following team conventions. Use when the user asks to create a ticket, issue, or task in Linear, or mentions tracking work, bugs, features, improvements, chores, or spikes.
Cierra una sesion dejando resumen, pendientes y mejoras con trazabilidad.
Skill especializada en gestión de alcance (scope) para Domain Storytelling, enfocada en ajustar la granularidad del modelado (coarse-grained "pájaro/cometa" vs fine-grained "mar/peces") y distinguir perspectivas temporales (As-Is proceso actual vs To-Be futuro deseado). Útil para definir el nivel apropiado de detalle según el objetivo del modelado y para gestionar expectativas entre stakeholders.
Converts PRDs/user stories into stable-ID requirements (REQ-xxxx), a structured test plan, a test case catalog (TEST-xxxx), and a traceability matrix. Supports iterative updates without renumbering IDs. Ships with pragmatic internal default and strict preset.
Product Manager role: MVP/MLP planning, feature prioritization (RICE, MoSCoW), roadmaps, backlog management, user story mapping, OKRs, lean canvas, jobs-to-be-done, value proposition, 9 product frameworks (MVP/MLP/MMP/MAC/RAT), Micro-MVPs, Continuous Discovery. 23 methodologies.
Integrated project management system with documentation, language initialization, and template optimization modules
Sequential reasoning with deep self-reflection and backtracking. Use when problems have step-by-step dependencies, need careful logical reasoning, or require error correction. Each step includes self-reflection, and incorrect steps trigger backtracking. Ideal for debugging, mathematical proofs, sequential planning, or causal analysis where order matters.
Pre-planning analysis to catch ambiguities, hidden requirements, and risks before work begins. Prevents wasted effort by surfacing problems upfront.
Business goals, stakeholders, and high-level context for this project.
Add PR breakdown plans to existing stories. Analyzes story complexity and proposes reviewable PR splits. Usage: /add-pr-breakdown [epic-file or story-id]
**v1.0 AGENTIC PIPELINE**: 6단계 에이전틱 아이디어 팩토리! 프로젝트분석→카테고리분류→아이디어기획(병렬)→기획팀장→PRD개발팀장→CTO최종결정. 4team-review 통합, 상위 0.001% 전문가 수준 기획문서 자동 생성.
作業計画の検証専門家。計画の完全性・明確性を検証し、見落としや曖昧さを指摘。使用場面: (1) 実装計画レビュー、(2) タスク分解の妥当性確認、(3) 依存関係の検証、(4) リスク特定、(5) スコープ確認。トリガー: "plan-reviewer", "計画", "レビュー", "タスク分解", "/plan-reviewer"
🛡️ Comprehensive security management for festivals including crowd control, threat assessment, emergency response, and staff coordination.
Review and score engineering specs against a quality rubric. Use when evaluating a spec draft before implementation to ensure it meets quality standards and identifies potential issues.