spec-flow-auto
SpecWorkflowMcpとAI連携による仕様駆動開発(SDD)完全自動化スキル。 PRD→SPEC→実装タスク→品質検証→Miyabi連携までを1コマンドで完結。 kiroやspec-flowの考え方を統合し、Claude Sonnet 4による高品質な仕様生成とタスク分解を実現。 あらゆるソフトウェア開発プロジェクトに適用可能な汎用SDDプラットフォーム。
Найдите подходящую возможность для вашего агента.
SpecWorkflowMcpとAI連携による仕様駆動開発(SDD)完全自動化スキル。 PRD→SPEC→実装タスク→品質検証→Miyabi連携までを1コマンドで完結。 kiroやspec-flowの考え方を統合し、Claude Sonnet 4による高品質な仕様生成とタスク分解を実現。 あらゆるソフトウェア開発プロジェクトに適用可能な汎用SDDプラットフォーム。
Retrieve memory summaries by ID, project, or recency. Returns structured JSON with compression metrics. Use to access compressed historical context for LLM prompts.
Generate comprehensive session summary for Leavn work - commits, metrics, achievements, remaining work, ship readiness
Loads project context, lists existing specs and changes, searches capabilities and requirements. Use when user asks about project state, existing specs, active changes, available capabilities, or needs context discovery. Triggers include "what specs exist", "show changes", "list capabilities", "project context", "find specs", "what's in the spec", "show me specs".
[21] UNDERSTAND. Deep research workflow for this project using 150% scope (100% core + 50% boundary), evidence-based reasoning, and structured investigation notes. Use when the task requires investigation, root-cause analysis, or mapping unknown areas. Always maintain a research log file that captures findings, hypotheses, and next branches; use web.run when external verification is needed.
Guides DDD discovery for the ToDo domain: ubiquitous language, bounded context, aggregates, invariants.
This skill should be used after productive sessions to extract learnings and route them to appropriate Reusable Intelligence Infrastructure (RII) components. Use when corrections were made, format drift was fixed, new patterns emerged, or the user explicitly asks to "harvest learnings" or "capture session intelligence". Transforms one-time fixes into permanent organizational knowledge by implementing updates across multiple files.
Transform codebase-search findings into phased execution plan. Creates workflow/tmp/plan-{task-name}.md, returns summary. Use after codebase-search completes.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Comprehensive DevOps and deployment workflow that orchestrates infrastructure automation, CI/CD pipelines, container orchestration, and cloud deployment. Handles everything from infrastructure as code and pipeline setup to monitoring, scaling, and disaster recovery.
Use after planning or implementing non-trivial tasks - runs Codex MCP background verification/review for quality gates (plan validation + implementation review)
GitHub issue workflow management with gh CLI and native dependency tracking. Use for gh commands, finding next issues, viewing issue dependencies, and claiming issues.
Routes tasks to reasoning frameworks and command patterns in commands-db. Triggers on structured development workflows, skill commands (sc:*), brainstorming, architecture, or any task matching command framework patterns. Uses reasoning-index for semantic routing.
Use when evaluating agent performance, building test frameworks, measuring quality, or asking about "agent evaluation", "LLM-as-judge", "agent testing", "quality metrics", "evaluation rubrics", "agent benchmarks"
Use this skill when the user needs help executing incident response workflows, investigating security incidents, containing threats, collecting forensic evidence, or performing remediation actions.
复审 plan-agent 生成的"预定清单(草案)"。触发:用户让你复审/分析/补全 plan-agent 的项目规划草案时使用;读取 draft-plan.md 并回写分析结果。
Transform PRD or story into complete page/component designs with ASCII layouts, component specs, interaction flows, and frontend implementation prompts. Use this skill when: - User asks to "design the page", "design component", "create page design" - User mentions "page design", "component design", "UI design", "layout design" - Running /frontend.design command - PRD or story is ready and need visual/interaction design before implementation - Need to create design spec that frontend developer can implement from Prerequisites: Design system must exist at docs/reference/frontend/design-system.md Output: ALWAYS write design files to docs/reference/frontend/designs/{name}.md
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKET_ID]" or similar phrases.
プロジェクトのアーキテクチャ構成図を生成するスキル。 インフラ、バックエンド、フロントエンドを解析し、Draw.io/Mermaid.js/PlantUML形式で可視化。 現状構成の把握、ドキュメント作成時に使用。