5,483 件 ・ 関連度順
概要と使いどころ
Workflow Phase 9 — Integration and Verification. Runs the full test suite, stamps the binding verdict at .claude/state/last_test_result, optionally runs a cross-engine smoke check, and writes harness_state so the harness auto-continues or yields. No subagent delegation.
日本語の概要は準備中です。原文の説明を表示しています。
Read-only view of the execution roadmap. Lists every epic with its per-status tallies, nests the still-open rows beneath their epic, collapses wholly-finished epics into one rollup line, and closes by naming the next planned task in file order. Four verbs — `list` (the reader's view), `tasks` and `epics` (filterable row and epic queries), `next` (the first planned task). Invoke any time to see what is left to build. Not a workflow phase; never writes; never starts or commits work.
日本語の概要は準備中です。原文の説明を表示しています。
Cycle-end retrospective converting recurring judgment failures into durable enforcement. Reviews the cycle's friction — repeated user corrections, guard trips, RCA themes, integrate failures — and turns each recurring one into a landmines.md entry, then proposes graduation candidates up the enforcement funnel (landmine → advisory hook → hard gate). Pairs with standup: standup says what shipped and what's next; retrospective says what kept going wrong and how to stop it structurally. Writes only memory entries and a report — graduation proposals are advisory and require the normal seed.md amendment path to become enforcement. Invoke at the end of a release cycle, an epic, or any stretch of work with repeated friction.
日本語の概要は準備中です。原文の説明を表示しています。
Write executable failing tests from a recipe handed to you by the main context. Used by `/tdd` Step 2 and ad-hoc when a phase needs tests-first to drive implementation. Decisions about which scenarios to cover, which categories matter, and which fixtures to use are made by the caller — this skill executes that recipe with code-structure discipline.
日本語の概要は準備中です。原文の説明を表示しています。
Preflight a spec draft without saving. Runs the same checks as the write-boundary hooks — PlantUML syntax, required diagram presence, AC-to-sequence traceability, Design calls quality floor, and System delta row resolution — and prints a compact pass/fail table. Use while iterating so the hooks don't bite on save.
日本語の概要は準備中です。原文の説明を表示しています。
Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.
日本語の概要は準備中です。原文の説明を表示しています。
Write a blog post in the preferred style related to amux
日本語の概要は準備中です。原文の説明を表示しています。
Use for the 5 Whys, or when the user wants the root cause of a failure: "why did this happen?", "this keeps breaking", "write the postmortem", "find the real cause". Asks why repeatedly with evidence at each step, then sets countermeasures. Skip for one-off typos or when the cause is already proven.
日本語の概要は準備中です。原文の説明を表示しています。
小说章节内容创作，适用于用户说"帮我写一章小说"、"续写接下来的内容"、"生成XX情节"、"批量写网文章节"、"扩写/重写这段内容"、"帮我写个XX情节"、"续写小说"、"把这段内容扩写"、"重写这一章"、"批量生成小说章节"、"写个开篇章节"、"写个高潮情节"、"小说内容生成"、"帮我写小说内容"等需求，支持单章/多章批量生成、续写、重写、扩写等多种模式，自动适配网文节奏，保持人物和剧情一致性，**批量生成时自动使用子Agent并行处理，每个Agent最多负责3个章节**
日本語の概要は準備中です。原文の説明を表示しています。
小说内容润色优化，适用于用户说"帮我润色这段小说"、"改下文笔"、"优化章节节奏"、"强化这个爽点"、"让对话更自然"、"把这段写得更爽"、"优化小说文笔"、"调整章节节奏"、"让对话更真实"、"帮我改下这段内容"、"润色小说"、"优化爽点"、"提升文笔"、"让这段更有代入感"等需求，提供3级润色等级，专注文笔与内容层面优化，支持风格适配、节奏收紧、爽点强化、对话优化等专项优化，**润色结果直接修改 chapters/ 目录，修改前自动备份到 .webnovel/write/original/**，**批量润色时使用子Agent并行处理，每个Agent最多负责3个章节**
日本語の概要は準備中です。原文の説明を表示しています。
小说逻辑/剧情审查，适用于用户说"帮我检查下小说有没有bug"、"看看时间线有没有矛盾"、"人物有没有OOC"、"找剧情前后冲突"、"梳理伏笔有没有回收"、"检查小说剧情合理性"、"看看有没有剧情漏洞"、"人物行为不符合性格"、"检查时间线对不对"、"找小说前后矛盾的地方"、"帮我梳理所有伏笔"、"小说剧情bug检查"、"逻辑漏洞排查"等需求，检测时间线冲突、逻辑漏洞、人物OOC、伏笔遗漏等问题，**执行字数检查确保章节字数达标**，**生成详细问题清单并自动修复所有问题，修复结果直接修改 chapters/ 目录，修改前自动备份到 .webnovel/write/original/**，**批量审查时使用子Agent并行处理，每个Agent最多负责3个章节**
日本語の概要は準備中です。原文の説明を表示しています。
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
日本語の概要は準備中です。原文の説明を表示しています。
Plan mode: write markdown plan to .hermes/plans/, no exec.
日本語の概要は準備中です。原文の説明を表示しています。
Write ML papers for NeurIPS/ICML/ICLR: design→submit.
日本語の概要は準備中です。原文の説明を表示しています。
Write implementation plans: bite-sized tasks, paths, code.
日本語の概要は準備中です。原文の説明を表示しています。
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and rewrite content to remove 21 categories of AI writing patterns with a 43-entry replacement table
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
日本語の概要は準備中です。原文の説明を表示しています。
Critically review a resume/CV against ATS (applicant tracking system) parsing rules, recruiter skim patterns, and keyword alignment with a target job description. Use when the user asks to "review my resume/CV", "check my resume against this job ad", "will this pass ATS", or shares a resume file (.docx/.pdf/.md) for feedback. Provides scored, prioritised, critical feedback — not a rewrite.
日本語の概要は準備中です。原文の説明を表示しています。
Rewrite AI-sounding prose so it reads as considered human writing — cut the tells (em-dash pile-ups, "it's not X, it's Y" antitheses, inflated vocabulary, uniform rhythm, empty uplift) while preserving every fact, claim, and the author's own voice. Use when the user says "make this not sound like AI", "de-AI this", "humanize/humanise this", "this reads like ChatGPT", "remove the AI tells", "it sounds robotic/generic", or shares a draft (post, email, essay, docs, cover letter) to sharpen into a more human voice. Ships a stdlib scanner that flags the mechanical tells.
日本語の概要は準備中です。原文の説明を表示しています。
Use for read-first Amazon Sponsored Products optimization, product-aware growth, preflight readiness, and post-change monitoring reviews that can run standalone from static exports or use Rocketcart MCP as an optional Amazon Ads plus product-intelligence layer. Guides Codex to inspect Rocketcart profiles, live SP campaigns, product ads/ASIN context, category rank/BSR movement, competitor signals, product readiness, budget and targeting drift, snapshots/changelogs, and proposed approval-gated action rows without executing writes by default.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Delphi / FreePascal / C++Builder code that reads, writes, manipulates, or exports Excel (.xlsx / .xls) files, generates PDF or HTML from Excel, or produces data-driven reports with FlexCel Studio for VCL and FireMonkey (TMS FlexCel). Triggers include Excel/xlsx from Delphi, TXlsFile, TFlexCelReport, TFlexCelPdfExport, TFlexCelHtmlExport, FireMonkey Excel export, Lazarus Excel, and Excel reporting from Pascal.
日本語の概要は準備中です。原文の説明を表示しています。
Makes sessions durable across `/clear`, machine reboots, and IDE switches. SessionStart catchup pulls scratch + last MemPalace recall + planning files into context. Stop promotion writes a handoff note and runs memory-keeper. Manual `/mddesign:handoff` re-runs either at any time.
日本語の概要は準備中です。原文の説明を表示しています。
How to write JSDoc on @rhinestone/sdk public symbols, which is autogenerated into the published SDK Reference. Use when adding or editing doc comments on entry points, the account instance, actions, or utils in sdk/src.
日本語の概要は準備中です。原文の説明を表示しています。