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.
่จญ่จๆธใฟๆฉ่ฝใฎTDDๅฎ่ฃ ใฏใผใฏใใญใผ
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.
wizใใญใธใงใฏใ้็บๆฏๆดในใญใซใspecs/ใใฃใฌใฏใใชใฎไปๆงๆธใๅ็ งใใTODOใฟในใฏใๅฎ่ฃ ใใใ ไฝฟ็จใฟใคใใณใฐ: (1) wizใใญใธใงใฏใใฎ้็บไฝๆฅญใ(2) specs/ใฎTODOใ้ฒใใใๆใ (3) ใๆฌกใฎใฟในใฏใใTODOใใๅฎ่ฃ ใใฆใใชใฉใฎ้็บใชใฏใจในใๆใ ไฝๆฅญๅฎไบๅพใฏdocs/ใๆดๆฐใใใ
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.