speckit-analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
Triage extension for JavaScript/TypeScript findings during plan-finalize phase
Create ATOMIC implementation plan for a single frontend task. Each step has 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 /frontend.plan command - User explicitly asks for "atomic steps", "step-by-step plan with verification" - Have a specific task from docs/reference/frontend/tasks/ and need implementation steps - Need granular steps: Setup (create files) → Implementation (write code) → Test (verify) → Commit 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.
Use when justifying technical debt to executives, calculating the cost of quality issues, translating tech metrics to business language, or planning quality budgets - uses research-backed formulas (2-3x defects, productivity multipliers) to convert code problems into dollars and ROI
Systematic planning and execution of system migrations including database migrations, platform changes, and technology stack transitions.
Create and manage development tasks after the user approves a plan. Initializes folders/files, updates the backlog, and keeps progress notes synchronized.
PCE (Process-Context Engine) の知識移転スキル。セッション/メンバー間での知識の連続性を確保し、引き継ぎを円滑にする。 トリガー条件: - 「引き継ぎ資料を作って」 - 「次の人に渡す情報をまとめて」 - 新メンバーのオンボーディング時 - 長期プロジェクトの節目 - 「プロジェクトの状況を共有して」
Analyze and resolve production incidents using systematic investigation, root cause analysis, and autonomous remediation
Sisyphus専用の実装フロー、Subtask処理、Phase別責任分担、チェックリスト、完了報告フォーマットを定義
Plan and review requirements with discovery/decision gating and approval. Use when requirements are unclear for a feature or refactor.
How to organize, structure, and keep a project plan up to date.
将 U1 的碎片化想法/问题归类为任务(tasks MCP)并按需沉淀为长期记忆(mem0-memory MCP)。
既存資料のREADME.mdを読み込み、推奨所要時間を再見積もりして更新するスキル。学習ガイド、チュートリアル、練習問題、実践課題の各資料タイプに対応し、章/ステップ/回ごとの目安時間と合計時間をテーブル形式で生成する。
Kanban Architect role. USE WHEN user says /kanban-architect OR wants to plan, assign, or monitor kanban tasks.
Zentrale Skill-Verwaltung für CONSYS-Projekt ohne Git-Abhängigkeit
Product management: PRDs, RICE prioritization, metrics
Manage plan lifecycle with status.toon and phase operations
A specialized skill for conducting employee performance appraisals at Moreh. It provides a structured evaluation process, rating scales, and detailed level-specific guidelines (from Level 1 to Level 9) to assess technical skills, problem-solving, and alignment with the 'Moreh Way'. Use this when evaluating performance or determining level-based expectations.
Skill for auditing and refining proposed objectives. Used to strictly verify alignment with SSOT/Context and compliance with SMART criteria, ensuring no gaps, waste, or feasibility issues exist before execution.
KPI for measuring first-pass verification success. Tracks how often verification passes on the first attempt. Use to reduce wasted cycles from verification failures.
Use when asked to "create state diagram", "map component states", "visualize state machine", "analyze state transitions", "document component behavior", or when needing to understand all paths through a component.
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.