603건 · 관련도순
Extract every PlantUML block from docs/specs/<slug>.md and render each to SVG under docs/specs/_rendered/<slug>/, with an index.md listing them in order. Run this before /approve-direction so the reviewer sees pictures instead of raw PlantUML.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when auditing UI code for interface-guideline compliance (accessibility, forms, animation, images, performance, UX copy) and/or validating a deployed page against Lighthouse 95+ targets. Produces evidence-based findings (file:line + Lighthouse JSON) and turns confirmed pendencies into Draft SPECs via write-specs. Do NOT use to design/build UI from scratch (use design) or to fix findings inline — fixes go through the SPEC pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when planning the migration of a legacy system or monolith — analyzes the source codebase (current repo, or a repo URL cloned to a temp dir) and produces an evidence-based Strangler Fig migration plan with per-domain SPECs. Default target is .NET (Blazor WebAssembly, .NET MAUI, ASP.NET Core); other stacks allowed by user decision. Do NOT use to implement code or when approved SPECs already cover the migration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrate legacy spec sources to artifact-first GitHub Issue specs. Supports local `specs/SPEC-*` directories and body-canonical `gwt-spec` Issues using the bundled migration script.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
dev-graph の1 featureを exact 13 task specsへ分解したいとき、独立評価後に13-entry inventory・13-node DAGを atomic promotionしたいときに使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Per-screen design spec generator for AI design tools (Stitch / Figma AI / Claude artifacts). Consumes per-feature PRDs from kta-prd-pipeline. Emits tool-agnostic markdown specs. Triggers — design spec, AI design prompt, screen mockup brief, Figma AI input, Stitch prompt, design system tokens, post-PRD design phase, generate design specs, design brief, mockup spec. DOES NOT generate Compose code, Kotlin code, or @Preview stubs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Per-screen design spec generator for AI design tools (Stitch / Figma AI / Codex artifacts). Consumes per-feature PRDs from kta-prd-pipeline. Emits tool-agnostic markdown specs. Triggers — design spec, AI design prompt, screen mockup brief, Figma AI input, Stitch prompt, design system tokens, post-PRD design phase, generate design specs, design brief, mockup spec. DOES NOT generate Compose code, Kotlin code, or @Preview stubs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert en design system markdown specs (73+ design systems as markdown, tokens, components)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
仕様書作成を支援するテンプレートスキル。 docs/specs/ への仕様書作成時に自動適用され、 01_REQUIREMENT_MANAGEMENT.md に準拠した構造を提案する。 要件定義、機能仕様、API仕様の作成時に活用される。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrator for spec-driven development (SDD) — the discipline of writing executable specs before code, with a constitution above them and a hard cross-check gate before implementation. Mirrors GitHub Spec Kit / AWS Kiro slash-command shape. Routes /constitution, /specify, /clarify, /plan, /tasks, /analyze, /implement to the right leaf skill. Load when the user says "spec-driven development", "SDD", "specs-first workflow", "run the spec loop", "/specify a feature", "/plan from this spec", "do spec-driven for this", "GitHub Spec Kit workflow", "Kiro workflow", or invokes any SDD-style slash command. Single entry point for all SDD workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Align explicit requirements, implicit expectations, non-goals, observable acceptance, evidence, and decision authority before OpenSpec specs and executable tasks finalize. Use when authoring or updating a proposal, design, specs, or tasks, or when a request hides a material product choice. Do not use for routine implementation of an already-authorized task, unrelated conversation, or facts the repository can answer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates detailed design briefs for social media creative assets. Covers image specs per platform, copy overlay text, color palette, and format specs for stories, carousels, singles, and reel covers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
업무와 일상의 반복 작업을 질문으로 구체화하고 시작 조건, 사람의 확인, 판단용 요약을 정리해 구현 담당자가 추가 질문 없이 만들 수 있는 워크플로 명세로 작성합니다.
색상·간격·글꼴을 공통 설정으로 정리하고 CSS 변수를 생성합니다. 화면 구성 요소의 상태별 규격과 코드의 직접 지정 값을 확인하며, 같은 브랜드 규칙으로 HTML 발표 자료를 만듭니다.
모호한 아이디어를 목표, 작업 범위, 검증 가능한 완료 조건이 담긴 명세로 정리합니다. 기능과 의존 관계를 나누고 사람의 승인을 거쳐 계획, 작업 분할, 구현으로 진행합니다.