Use when the user asks to generate, update, refresh or verify project documentation, or to check that docs still match the codebase. Writes up to 9 doc files, each verified against real paths; supports --force and --verify-only.
The English summary is being prepared. Showing the original description.
Use when a GSD run failed, stalled, or produced the wrong result and the cause is unclear. Reads git history and .planning/ state and phase artifacts to diagnose root cause, then writes a report to .planning/forensics/.
The English summary is being prepared. Showing the original description.
Use when a milestone audit reported gaps and you want the fix phases created in one pass. Reads MILESTONE-AUDIT.md, groups gaps into phases, adds them to ROADMAP.md and offers to plan each one.
The English summary is being prepared. Showing the original description.
Use after a phase has been discussed, or when the user asks for a PLAN.md for a roadmap phase. Researches, spawns gsd-planner, verifies with gsd-plan-checker, and iterates; supports --gaps, --prd, --skip-research.
The English summary is being prepared. Showing the original description.
Use when the user asks where the project stands, what to do next, or to resume after a break. Summarizes recent work and what is ahead, then routes to executing an existing plan or planning the next one.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when the user wants to see what the agent assumes about a phase's approach, order, scope, risks and dependencies before planning starts, instead of running a full discuss session. Read-only; ends with a prompt for feedback.
The English summary is being prepared. Showing the original description.
Use when .planning/ looks inconsistent, files are missing, or state seems wrong. Validates .planning/ integrity, reports missing files, bad config, and orphaned plans, and --repair fixes what it finds.
The English summary is being prepared. Showing the original description.
Use when the user asks what UAT or verification items are still outstanding across phases, or wants a prioritized manual test plan. Scans every phase for pending, skipped, blocked and human_needed items and flags stale docs.
The English summary is being prepared. Showing the original description.
Use when the user asks for a knowledge article, wiki page, or entity summary from the brain, or wants to search, list, or review merges across brain DB articles. Generates Wikipedia-style articles from entities, decisions, and emails.
The English summary is being prepared. Showing the original description.
Trading Super Intelligence Team. Named real-world personas across 8 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.
The English summary is being prepared. Showing the original description.
End-of-session brain flush. Scans the full conversation, extracts all new entities, decisions, tasks, events, relationships, and updates, presents a summary, and writes to project_brain.db after confirmation. Use at end of every session or when you want to capture everything discussed.
The English summary is being prepared. Showing the original description.
Use when the user asks to make an existing website or app look premium, remove generic AI-looking design, or polish a UI without changing functionality. Audits the stack, lists the generic AI patterns, and upgrades in place.
The English summary is being prepared. Showing the original description.
Use when the user asks to create, scaffold, update or package a skill, or asks how skill frontmatter, progressive disclosure or bundled resources should be structured. Walks through init_skill.py, writing SKILL.md and package_skill.py.
The English summary is being prepared. Showing the original description.
Your climate and energy brain trust. 25 named personas across 7 cells covering energy transition, carbon markets, climate modeling, sustainability, grid infrastructure, environmental policy, and ESG.
The English summary is being prepared. Showing the original description.
Use when executing implementation plans with independent tasks in the current session
The English summary is being prepared. Showing the original description.
Strategy Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.
The English summary is being prepared. Showing the original description.
Guides users through creating effective Agent Skills for Cursor. Use when the user wants to create, write, or author a new skill, or asks about skill structure, best practices, or SKILL.md format.
The English summary is being prepared. Showing the original description.
Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery/research, growth/metrics, design foundations/usability, design leadership/craft, UX/content, design systems, and a…
The English summary is being prepared. Showing the original description.
Use when the user says I want to add X, implement Y, create a task for Z, or plan this feature. Writes a task file plus a PRD under .agent/, links them, and waits for approval before any implementation starts.
The English summary is being prepared. Showing the original description.
Use when the user says 'cognee recall', 'search memory', 'what do we know about', 'find related', or 'graph search'. Runs semantic, graph, and lexical search across the Cognee knowledge graph and injects results as agent context.
The English summary is being prepared. Showing the original description.
Your legal, IP, and regulatory brain trust. 31 named personas across 7 cells covering patent strategy, tech licensing, regulatory litigation, AI governance, open-source compliance, privacy law, and antitrust.
The English summary is being prepared. Showing the original description.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
The English summary is being prepared. Showing the original description.
Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, and other visual explanations.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)