vertical-slice-roadmap-planner
Read a vertical slice GDD and generate a phased roadmap of features that need to be implemented, organized into logical phases with high-level feature descriptions.
Read a vertical slice GDD and generate a phased roadmap of features that need to be implemented, organized into logical phases with high-level feature descriptions.
้กน็ฎ่ทฏๅพ่งๅไธๆง่กๅฉๆใๅธฎๅฉๅๆ้กน็ฎ้ๆฑใ่งๅๆง่ก่ทฏๅพใๅ่งฃไปปๅกใ่ฏๅซ้ฃ้ฉใ็ฎก็่ฟๅบฆ๏ผ็กฎไฟ้กน็ฎ้ซ่ดจ้ไบคไปใ
Project state management using CONTEXT.md files with Past/Current/Future sections. Use when: "project context", "CONTEXT.md", "project status", "where are we", "project state".
Plan and document features before implementation using project templates. Use when planning new features, creating architecture docs, or when user mentions "plan", "design", "architect", "feature plan", "implementation plan", or "before coding".
Create ATOMIC implementation plan for a single backend task. Each step has TDD, exact code, and verification command. IMPORTANT: This skill creates MICRO-LEVEL atomic steps, NOT macro architecture plans. For architecture planning or feature scoping, use EnterPlanMode instead. Use this skill when: - Running /backend.plan command - User explicitly asks for "atomic steps", "step-by-step plan with verification" - Have a specific task from docs/reference/backend/tasks/ and need implementation steps - Need granular TDD steps: Types โ DB โ Test (failing) โ Implementation โ Test (passing) โ API DO NOT use for: - Architecture planning (use EnterPlanMode) - General development planning - Feature scoping or estimation Output: Present plan to user (not saved to file), each step includes Files, Action, and Verify command.
Strengthens CV bullet points by adding specific metrics, percentages, timescales, and quantifiable results.
Generate structured handoff for session transitions or task boundaries. Use before clearing session, after completing a task group, or when context degradation is suspected.
็พๅจใฎ็ถๆณใใฟในใฏใซๅใใใฆใไปไฝฟใในใใในในใกใฎในใญใซใๆๆกใใ
Skill for identifying the gap between a user's request and the project's current reality (code, existing ADRs, and documentation). Used for (1) uncovering discrepancies between intent and implementation, (2) gathering factual evidence from the codebase and SSOT, and (3) establishing a grounded starting point for new architectural decisions.
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