9K skills · sorted by relevance
This skill should be used when the user asks to "dev-webtest-plan", "Webテスト計画を生成", "テスト計画を作成", "webtest plan", "E2Eテスト計画", "画面テスト計画", "generate webtest plan", "create test plan from requirements", "webtest計画を更新", "テスト計画の差分更新", "update webtest plan", "画面仕様からテスト更新". dev-planの出力からPlaywright用のWebテスト計画ファイルを自動生成する。画面仕様の変更差分からテスト計画を更新する差分更新モードも対応。
The English summary is being prepared. Showing the original description.
Produce a high-confidence, CONCISE implementation / architecture / strategy PLAN that follows the OMC plan system end to end. It first runs OMC's real requirements interview (auto-chains the `omc-plan` skill: one question at a time, explore-first, Analyst consult) to produce an initial plan in `.omc/plans/`, then DEEPENS that plan with a 3-round ITERATIVE fusion loop — each round an Opus 4.8 panelist (Agent subagent) and a GPT-5.5 panelist (via codex) critique/improve it IN PARALLEL and BLIND, then Opus 4.8 (the orchestrator) judges and synthesizes one tighter plan that seeds the next round, stopping early on convergence. Writes the final dense plan back to the same `.omc/plans/<slug>.md`, then offers the OMC handoff (`/omc-plan --review` → `/team` or `/ralph`). Use for high-stakes planning, architecture decisions, strategy calls, and hard debugging — especially when the user runs /plan or asks how to approach a non-trivial build. Reuses the `fusion` skill's run_codex.sh + judge rubric. NOT for trivial tasks (single pass is enough).
The English summary is being prepared. Showing the original description.
Audit GitHub issues to find open work outside a masterplan, distinguishing missing parents from missing plan ancestors. Preview or apply removal of closed issues from the hierarchy while keeping their open children connected to the plan.
Create text diagrams with PlantUML for README files, emails, and terminal workflows. Convert diagram definitions into plain ASCII or Unicode box-drawing output to share interactions and relationships where image-based diagrams are unsuitable.
Organize multi-step agent tasks with persistent Markdown files for plans, findings, and progress. Records decisions, errors, and test results, then reloads the selected task's planning files to resume work after an interruption.
Turn a development phase into an actionable PLAN.md through research, planning, and verification. The skill can incorporate requirements or recorded design decisions, then check and revise the plan before presenting the results.
Validate an implementation plan before execution through structural checks and specialist agent reviews. Check dependencies, files, tests, and architectural decisions, then update the plan to resolve findings, requesting human decisions when existing guidance is insufficient.
Translate existing code-explanation docs into another language, Chinese by default. Translates a whole `CODE_EXPLANATION/` folder into a parallel `CODE_EXPLANATION_<LANG>` copy (e.g. `CODE_EXPLANATION_ZH`), or a single file — either bilingually in place (English + translation interleaved) for small files or as a `<name>_<lang>.<ext>` sidecar copy for larger ones. Keeps filenames, code, identifiers, file paths, and technical terms in English — only the explanatory prose is translated. Use this skill whenever the user wants to translate, localize, or produce a non-English version of code-explanation / codebase documentation: phrases like "translate-explanation", "translate the code explanation", "translate the CODE_EXPLANATION folder", "localize these docs to Chinese", "make a Chinese version of the explanation", or naming any target language for the explanation files. Default to Chinese (ZH) when no language is specified.
The English summary is being prepared. Showing the original description.
Convert agreed scope into a structured matter plan — phases, workstreams, milestones, dependencies, owner assignments, and matter setup decisions. Use when planning a new matter, running a kickoff, building a workstream plan, structuring phases, setting up task codes, or producing a plan to drive status reporting. Trigger on: 'build a plan', 'matter plan', 'project plan', 'what are the phases', 'workstream plan', 'how do we sequence this', 'who owns what', 'task codes', 'matter setup', 'workstream plan', 'matter plan', 'rolling wave', 'plan the next phase', 'what comes first', 'kickoff agenda'.
The English summary is being prepared. Showing the original description.
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.
The English summary is being prepared. Showing the original description.
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.
The English summary is being prepared. Showing the original description.
Execute the tasks from an already-created feature plan in .unikit/code/plans/ — read the plan manifest (the PLAN.md file in the plan folder), work through the uncompleted tasks in order, write the code, mark progress, and resume across sessions. Supports selective runs by phase or by task numbers, and continuing from where the last session stopped. Use whenever a plan exists and the user wants to build it, e.g. "implement", "implement the plan", "start coding", "execute the plan", "run the plan", "do the next task", "implement phase 3", "implement tasks 2.1 and 2.3", "continue implementation", "continue where we left off", "keep going on the feature". To create the plan first, use the planning skill — this one carries an existing plan out.
The English summary is being prepared. Showing the original description.
Use when the user just says "plan", "planen" or "roadmap": offer a template via aos-plan-canvas templates. Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use for planning, whenever a user says "plan", "roadmap", "visualize the plan", "review the plan" or /plan-canvas, right after a brainstorm or grill interview has produced a plan, and whenever any skill's artifact (plan, design, comparison, report, diagram) can be reviewed visually instead of with typed feedback.
The English summary is being prepared. Showing the original description.
Write or revise a Paperclip plan that states the intended outcome, constraints, approach, and success checks. Capture unresolved decisions, maintain the saved plan, and request approval when the work requires it.
Coordinate a development task from planning through implementation and review. Choose whether to proceed after seeing the plan, then receive a report covering commits, verification results, review findings, and any work left unfinished.
Turns implementation requests into concise work plans with file references, testable acceptance criteria, risks, and verification steps. It can clarify vague requirements through focused questions, generate a plan directly, or review an existing plan.
Build or refresh a strategic customer account plan from sales records, emails, and meeting transcripts. Organize goals, stakeholders, growth opportunities, risks, and dated actions into a document, then sync approved highlights to the customer relationship management system.
Organize multi-step research and project work with Markdown files for plans, findings, and progress. Gemini hooks, automatic actions at session events, surface planning context so the agent can resume from saved records.
Import an external plan into GSD after checking it against recorded project decisions, then validate the resulting plan file. It also supports converting a GSD-2 project back to the GSD v1 planning format.
Open documents, text configuration files, HTML, URLs, or folders in Plannotator for browser review. The agent responds to returned annotations and can use an approval session when you need to accept a plan, specification, or document.
Turn an idea into a goal package for /goal. Collect decisions through Plannotator, review testable requirements, explore the codebase, and produce an approved execution plan with verification steps and a clear completion condition.
Use when the next period ADS plan must be built from last period results — read the report and the audit, keep and scale winners, stop or fix losers, set new test hypotheses, split budget, plan three budget scenarios, and schedule the creative pipeline. Trigger on 'next month ads plan', 'plan ads from the report', 'what should we run next month', 'Q4 ads plan', 'next quarter media plan', 'the month ended, now what'. Also use when a report and an audit both exist and no decisions have been made. Not for — the first media plan before any data, see `54-media-plan-global`; scoring the account, see `21-ads-audit-global`; the next period CONTENT plan, see `40-next-content-plan-global`.
The English summary is being prepared. Showing the original description.
Execute an implementation plan file produced by $draft-plan or $turboplan. Runs pre-implementation prep, then runs $implement to execute the steps and finalize once they are all done. Use when the user asks to "implement plan", "implement the plan", "execute the plan", "run the plan", "implement plans/<slug>.md", "start implementing the plan", or starts a fresh session to implement a previously drafted plan.
The English summary is being prepared. Showing the original description.
Execute an implementation plan file produced by /draft-plan or /turboplan. Runs pre-implementation prep, then runs /implement to execute the steps and finalize once they are all done. Use when the user asks to "implement plan", "implement the plan", "execute the plan", "run the plan", "implement plans/<slug>.md", "start implementing the plan", or starts a fresh session to implement a previously drafted plan.
The English summary is being prepared. Showing the original description.