speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
Design-implementation gap analysis, code quality analysis, and report writing patterns. Used in PDCA Check phase for verification and quality assurance. Triggers: gap analysis, code review, quality check, ์ค๊ณ-๊ตฌํ ๋ถ์, ใฎใฃใใๅๆ, ๅทฎ่ทๅๆ
็ปไธไปปๅก็ฎก็ๆ่ฝ๏ผไฝฟ็จ GitHub Issues ็ฎก็ๆๆ Agent ไปปๅก๏ผๆฏๆไปปๅกๅๅปบใๆดๆฐใ่ฟฝ่ธชๅๅฎๆ
Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems.
ใใใฑใผใธ/ใขใธใฅใผใซๆง้ ใฎๅๆใจใชใใกใฏใฟใชใณใฐๆฏๆดใๅพช็ฐไพๅญใฎๆคๅบใ่ฒฌๅๅ้ขใฎๆๆกใ็งป่ก่จ็ปใฎไฝๆใ่กใใใใใใฑใผใธๆง้ ใ่ฆ็ดใใใใใใขใธใฅใผใซใฎไพๅญ้ขไฟใ่ค้ใใใใกใคใซ้ ็ฝฎใๆด็ใใใใใๅพช็ฐไพๅญใ่งฃๆถใใใใใจใใฃใๆง้ ๆนๅใชใฏใจในใใง่ตทๅใ
Project planning methodologies including work breakdown structure, task estimation, dependency management, risk assessment, sprint planning, and stakeholder communication. Use when breaking down projects, estimating work, planning sprints, or managing dependencies.
ๆบ่ฝๅ่ฐๅจ๏ผ็ผๆๅคไธชๆ่ฝๅๅฝไปคๅฎๆ็ซฏๅฐ็ซฏ็ๅทฅไฝๆตใ่ชๅจ่งๅๅๆง่กๅคๆ็ๅคๆญฅ้ชคไปปๅกใ
Execute the implementation planning workflow using the plan template to generate design artifacts.
Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.
Guide prospective hindsight analysis to identify project risks before failure occurs. Teams imagine the project has failed spectacularly, then work backward to identify causes. Increases risk identification by 30% compared to traditional planning.
Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.
Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Track TODOs in project-specific markdown files in ~/Desktop/TODO/.
Enforces a structural planning phase before execution. Generates and validates PLAN.json to ensure every task has a clear objective, steps, verification method, and rollback strategy.
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
Entry point for ALL work requests - triages scope from trivial to massive, asks clarifying questions, and routes to appropriate planning skills. Use this when receiving any new work request.
Use when preparing executive reports, evaluating investments, or calculating ROI/break-even/payback period. 30-minute analysis (87.5% time saving). Includes scenario analysis.
Systematic analysis and reasoning workflows. Use when performing audits, investigation, requirements analysis, risk analysis, scenario/edge-case enumeration, or design analysis that demands evidence-based, comprehensive coverage.
Alice's couch-to-5K personal extensions with running metrics and training data.
้็จใฉใณใใใฏใฎไฝๆใปไฟๅฎในใญใซใๆฌ็ชใทในใใ ใฎ้ๅฎณๅฏพๅฟใใใฉใใซใทใฅใผใใฃใณใฐๆ้ ใ ใชใซใใชใผใฏใผใฏใใญใผใ้็จ็ฅ่ญใฎๅ ฑๆใๆจๆบๅใใไฟก้ ผๆงใฎ้ซใใทในใใ ้็จใๅฎ็พใใใ Anchors: โข Site Reliability Engineering (Google) / ้ฉ็จ: ใฉใณใใใฏใใฟใผใณใใในใใขใผใใ / ็ฎ็: ้็จใฎๅ่ถๆงใจไฟก้ ผๆง โข The Practice of System and Network Administration (Limoncelli) / ้ฉ็จ: ๆ้ ๆธๆจๆบๅ / ็ฎ็: ๅ็พๅฏ่ฝใช้็จ โข Incident Management for Operations (Mogull) / ้ฉ็จ: ใคใณใทใใณใๅฏพๅฟ / ็ฎ็: ๅนๆ็ใชๅฑๆฉๅฏพๅฟ Trigger: Use when creating runbooks, documenting incident procedures, standardizing operational workflows, building troubleshooting guides, establishing recovery procedures, improving on-call readiness. runbook, incident response, troubleshooting, recovery procedures, operational documentation, on-call playbook