Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.
日本語の概要は準備中です。原文の説明を表示しています。
talmolab/sleap☆ 6182026年10月13日 更新
Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution.
日本語の概要は準備中です。原文の説明を表示しています。
nWave-ai/nWave☆ 6172026年9月16日 更新
Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification.
日本語の概要は準備中です。原文の説明を表示しています。
nWave-ai/nWave☆ 6172026年9月16日 更新
Creates evidence-based documentation following DIVIO/Diataxis principles. Use when writing tutorials, how-to guides, reference docs, or explanations.
日本語の概要は準備中です。原文の説明を表示しています。
nWave-ai/nWave☆ 6172026年9月16日 更新
Monthly, and on its first run it is the whole setup, launched by hand. It discovers what the member actually runs by walking their code roots and reading the registrar, the host, and the hosted database, then writes the inventory, the domains file, the starting budgets, and the opening safe fix rules, seeds the board, builds the dashboard, and registers one scheduled job per routine. It creates no account, buys nothing, and provisions nothing.
日本語の概要は準備中です。原文の説明を表示しています。
markfulton/ai-employees☆ 6132026年10月10日 更新
Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces, reads the member's own already published posts, and builds the voice file from real samples rather than from an idea of a voice, then writes the plan, creates the proof inventory, seeds the opening slots, and registers the recurring jobs. On every monthly run it re reads the evidence the kit produced and rebuilds only what the evidence contradicts. It publishes only where you released the channel, never replies, spends only where you released it, and it never enters a credential.
日本語の概要は準備中です。原文の説明を表示しています。
markfulton/ai-employees☆ 6132026年10月10日 更新
Monthly, browser conditional. On its first run it discovers the member's properties from the sites they name, writes the three strategy files, creates every ledger and folder the kit reads, files the opening cards, and registers the eight scheduled jobs. Every month after that it re-reads the evidence rather than its own previous conclusions, rebuilds the topic map and the internal link map, corrects any property fact it can prove wrong, and records every change with the path of the evidence that forced it. It holds publishing and spending unless you released the channel, and it never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
markfulton/ai-employees☆ 6132026年10月10日 更新
Runs once by hand on the first day and once a month after that, light browser lane. On the first run it researches the business from its own published surfaces before asking anything, writes the strategy folder, creates the ledgers, seeds the opening cards, builds the single page dashboard, reconciles the schedule table, and registers the eight recurring jobs. On every monthly run it re-reads a month of the kit's own evidence, applies what changed, adds a tab for a channel that gained volume, rebuilds, and reconciles every registered job against the table. It holds every outbound action unless you released the channel, and it never enters a credential.
日本語の概要は準備中です。原文の説明を表示しています。
markfulton/ai-employees☆ 6132026年10月10日 更新
Monthly on the last weekday, light browser lane. Re-tests every theme and every severity rule against a month of real ticket evidence and rewrites strategy/themes.md wherever the evidence disagrees with the assumption. It merges two themes the evidence shows are one, splits a theme whose tickets have two different answers, retires a theme with no volume, creates a theme for a cluster that kept landing unclassified, and rewrites a severity rule wherever the outcomes contradict it. Theme ids are never reused and never renumbered. It holds every outbound action unless you released the channel, and it never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
markfulton/ai-employees☆ 6132026年10月10日 更新
Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, reads the account structure once, writes the plan folder, seeds the board, creates the creative doctrine, builds the dashboard, and registers the recurring jobs. It asks about exactly two things, the monthly ceiling and the daily cap, because those are the two numbers that decide how much money can leave. On every monthly run it re reads the evidence, corrects what the ledgers prove wrong, and reconciles drift.
日本語の概要は準備中です。原文の説明を表示しています。
markfulton/ai-employees☆ 6132026年10月10日 更新
Weekly. Audits the paid and measurement setup the member already has by reading it, then assembles the parts that are missing as local files: campaign structure, ad copy, negative keyword seeds, and conversion tracking specifications, each one complete and ready to paste. It creates nothing in an account, saves nothing, activates nothing, and spends nothing, unless you released the channel. This is where the spend stop lives.
日本語の概要は準備中です。原文の説明を表示しています。
markfulton/ai-employees☆ 6132026年10月10日 更新
Weekdays. The only routine in this kit that opens a screen inside an account that can spend, and everything it does there is read. It confirms the primary conversion event still fired inside the read window before it trusts any other figure, then reads yesterday's spend, delivery, and result rows at account, campaign, ad set, and creative level and appends one row per object per day to the daily metrics ledger with the screen, the date range, and the read date beside every figure. It creates nothing, saves nothing, activates nothing, and spends nothing, unless you released the channel.
日本語の概要は準備中です。原文の説明を表示しています。
markfulton/ai-employees☆ 6132026年10月10日 更新
Use when starting work on a PERSONAL brand — a founder, coach, or creator, not a company: creates `.agents/personal-brand-context-global.md` covering story, expertise, audience, positioning, platforms, visual identity, and the asset inventory of style refs, face refs, logo, palette, and background, with region variants for US, EU, SEA, and LATAM. Skills 23 to 28 read it first. Trigger on 'personal brand setup', 'set up my founder brand', 'coach personal brand context', 'creator profile setup', 'the AI does not know my story', 'build my personal brand from zero'. Not for — a company or product brand, see `00-marketing-plan-global` and `product-marketing-context-global`; the 12-month strategy built on this, see `23-personal-brand-strategy-global`.
日本語の概要は準備中です。原文の説明を表示しています。
minhnv0807/ai-business-skills☆ 6132026年9月12日 更新
Use when starting work on a new product, client, or market — this skill creates the file `.agents/product-marketing-context-global.md` that 60+ other global skills read before they write anything: product, ICP, positioning, proof, objections, brand voice, pricing, and KPIs, with a region variant for US, EU, SEA, or LATAM. Run once, reuse forever. Trigger on 'set up marketing context', 'new client setup', 'onboard a new product', 'the AI does not know my product', 'US marketing context', 'EU GDPR setup', 'SEA market context', 'LATAM setup'. Also use when the user complains every answer comes back generic because nothing about the business was ever provided. Not for — a personal brand belonging to a founder, coach, or creator, see `22-personal-brand-context-global`; deep persona and JTBD research, see `09-customer-insight-global`; the period plan itself, see `00-marketing-plan-global`.
日本語の概要は準備中です。原文の説明を表示しています。
minhnv0807/ai-business-skills☆ 6132026年9月12日 更新
Zero-config goal-to-tasks engine. Takes any goal (software, pentest, business, learning), runs adaptive discovery, generates a validated spec, parses into TaskMaster tasks, creates an implementation plan, and executes with built-in CDD verification. Use when user says "PRD", "product requirements", "I want to build", or any goal-driven phrase.
日本語の概要は準備中です。原文の説明を表示しています。
anombyte93/prd-taskmaster☆ 6072026年8月14日 更新
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
日本語の概要は準備中です。原文の説明を表示しています。
ECNU-ICALK/AutoSkill☆ 6012026年5月10日 更新
Knowledge comic creator supporting multiple art styles and tones. Creates original educational comics with detailed panel layouts and sequential image generation. Use when user asks to create "知识漫画", "教育漫画", "biography comic", "tutorial comic", or "Logicomix-style comic".
日本語の概要は準備中です。原文の説明を表示しています。
ECNU-ICALK/AutoSkill☆ 6012026年5月10日 更新
Generates professional slide deck images from content. Creates outlines with style instructions, then generates individual slide images. Use when user asks to "create slides", "make a presentation", "generate deck", "slide deck", or "PPT".
日本語の概要は準備中です。原文の説明を表示しています。
ECNU-ICALK/AutoSkill☆ 6012026年5月10日 更新
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.
日本語の概要は準備中です。原文の説明を表示しています。
coco-research/coco☆ 5962026年10月13日 更新
Use after /gsd-verify-work passes, when the work should become a PR. Pushes the branch, creates the PR with an auto-generated body, optionally triggers review, and tracks the merge, closing the plan-execute-verify-ship loop.
日本語の概要は準備中です。原文の説明を表示しています。
coco-research/coco☆ 5962026年10月13日 更新
Use when you need an isolated copy of one or more repos with its own .planning/, or want to work on several repos in parallel. Creates worktrees or clones plus WORKSPACE.md; then run /gsd-new-project inside.
日本語の概要は準備中です。原文の説明を表示しています。
coco-research/coco☆ 5962026年10月13日 更新
Use when the user wants to park an idea or feature request that is not ready for active planning, or says add it to the backlog. Writes a 999.x entry to ROADMAP.md and creates its phase directory for later promotion.
日本語の概要は準備中です。原文の説明を表示しています。
coco-research/coco☆ 5962026年10月13日 更新
Use when opening a pull request and the diff is cluttered with .planning/ commits. Creates a clean branch filtered of GSD planning artifacts so reviewers see only code changes.
日本語の概要は準備中です。原文の説明を表示しています。
coco-research/coco☆ 5962026年10月13日 更新
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
日本語の概要は準備中です。原文の説明を表示しています。
coco-research/coco☆ 5962026年10月13日 更新