Use for implementation, review, refactoring, migration, or diagnosis in a React 18 or React 19 project built with Vite 7 when the task requires React design judgment, version compatibility, or a Vite client build decision. The primary scope is browser-rendered CSR SPA/MPA and Vite client builds embedded in an existing backend. Do not use by default for non-Vite React, React 17 or earlier, React 20 or later, Vite 6 or earlier, Vite 8 or later, framework-owned SSR/RSC/server functions, or isolated copy and styling work.
Generate an executable implementation work-plan Markdown at `docs/briefs/` from planning notes or a rough task description, with the plan body written in caveman **full** mode as a register-only transform that preserves every fact, bullet, execution stage, field, and section depth from the normal-mode equivalent. Work brief, task brief, handoff brief, implementation ticket, and task spec remain trigger aliases. Nine required sections keyed to Conventional Commits types so coding agents switch behavior (refactor → preserve, fix → reproduce first, perf → measure first). Briefset mode emits a parent execution-management document plus N child briefs when the input describes multiple execution contexts. Chat / questions / status reporting stay in normal prose — caveman applies to the saved file only. Use only when the user explicitly asks for the caveman register or invokes this skill by name; for normal-prose briefs use task-brief-creator instead.
Generate an executable implementation work-plan Markdown at `docs/briefs/` from planning notes or a rough task description. Work brief, task brief, handoff brief, implementation ticket, and task spec remain trigger aliases. Nine required sections are keyed to Conventional Commits types so coding agents switch behavior (refactor → preserve, fix → reproduce first, perf → measure first). Briefset mode emits a parent execution-management document plus N child briefs when the input describes multiple execution contexts. Manual trigger only — use when the user explicitly invokes this skill or asks for a work plan, implementation plan, work brief, task brief, handoff brief, implementation ticket, or task spec for a coding agent. Not for prose summaries, status reports, design docs, or meeting notes. For the plain-language caveman variant, use task-brief-creator-caveman instead.
Use only when the user explicitly invokes this skill.
Analyze repository structure and generate or update standardized AGENTS.md files that serve as contributor guides for AI agents. Supports both single-repo and monorepo structures. Measures LOC to determine character limits and produces structured documents covering overview, optional ownership maps, patterns, conventions, and working agreements. Update mode refreshes only the standard sections while preserving user-defined custom sections, and only modifies AGENTS.md files previously generated by this skill — externally-authored files are reported, never rewritten. Use when the user wants an AGENTS.md generated or refreshed — setting one up for a new repository, onboarding AI agents to an existing codebase, updating an existing AGENTS.md after meaningful project changes, or when the user mentions AGENTS.md. Not for CLAUDE.md, README, or other documentation files.
Orchestrate a large task as a manager-run sequence of isolated sub-agent phases when the user explicitly invokes this skill or asks for this. The main agent decomposes the task into phases of different kinds, picks the topology that fits (linear pipeline, parallel fan-out, dependency DAG, or iterative loop), assigns each phase a capability-by-deliberation tier, and runs each as a fresh isolated sub-agent exchanging file paths only -- never doing phase work itself. It proves any expensive step cheaply before committing, and halts for the user at up to two points: go/no-go before that commitment, and accept/reject on review findings. Runs are resumable by run id; a changed condition re-versions the prior run. For large heterogeneous work: research sweeps, multi-variant runs, migrations, audits. Explicit-invocation only. Not for single-artifact build-review-improve loops (use delegated-review-loop) or single-answer blind verification (use iterative-self-review).
Create, update, or fact-check a Feature Design Doc that captures product/system design decisions for downstream code agents. Use whenever the user mentions "기능 문서", "기능 설계 문서", "Feature Design Doc", "FDD", "design doc", or asks to write, draft, generate, update, revise, review, validate, fact-check, audit, or normalize a feature document — even when the user does not explicitly use the word "design", and especially right after a feature was ideated and implemented in-session (vibe-coding) and now needs documenting. Trigger on near-misses like "기능 정리 문서 좀 써줘", "이 문서 좀 검토해줘 우리 기능 design 관련이야", or "design doc 좀 만들어볼래". NOT for system/architecture design docs, RFCs, implementation plans, task lists, or READMEs — the subject must be a single product feature. This skill enforces that the artifact remains a decision source, not an implementation plan or task list, so use it whenever the working artifact is meant to drive what a feature *is* rather than *how it gets built*.
A skill that analyzes user requirements to generate system prompts ready for evaluation. It determines whether a single or multi-prompt architecture is needed and queries for missing information if requirements are insufficient. Use when asked to create, design, or draft a system prompt for an LLM-powered bot, assistant, classifier, router, or multi-step prompt pipeline (e.g. "create a system prompt", "시스템 프롬프트 만들어줘", "분류기 프롬프트 짜줘"). Not for refining an existing prompt, one-off user prompts, agent definition files, CLAUDE.md/AGENTS.md, or Claude Code skill definitions.