Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
1.3万 件 ・ 関連度順
概要と使いどころ
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Execute the implementation planning workflow using the plan template to generate design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
日本語の概要は準備中です。原文の説明を表示しています。
Write clean, readable, and maintainable code following principles from Robert C. Martin's "Clean Code" and Object Calisthenics. Use when writing, reviewing, or refactoring code to improve naming, function design, formatting, error handling, and class structure. Includes code smell detection and refactoring guidance.
日本語の概要は準備中です。原文の説明を表示しています。
[Frontend] Use when designing beautiful or aesthetic interfaces with curated UI styles, palettes, fonts, charts, and stacks.
日本語の概要は準備中です。原文の説明を表示しています。
[Research] Use when starting a web research task — discover, gather, and triage candidate sources on a topic to feed deeper investigation.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when you need to perform a security review or audit on any scope — application code (OWASP Top 10 2025), secrets exposure, dependency/supply-chain malware, third-party repository vetting before install, infrastructure/config, CI/CD pipeline, AI-agent risks, and host/VPS compromise detection.
日本語の概要は準備中です。原文の説明を表示しています。
[Process] Use when the developer wants something explained or taught, or wants to know HOW TO REVIEW a change — by default the current working tasks + changes in context, or whatever the prompt names (a plan, a subsystem, a decision, a concept, a bug). AI derives WHAT to explain from the prompt and ALWAYS delivers a teacher-and-coach review guide, high level first then detail: what was done, a VISUAL MAP (system flowchart, domain ERD, sequence diagrams), the user stories and business rules with their REAL test-case IDs, a REVIEW PATH naming which files to open first and in what order with an exit criterion per stage, the technical concepts needed to follow it, how it works, why THIS solution, every alternative option with pros/cons, the trade-offs accepted, the blast radius, HOW TO TEST AND DEMO the change, the developer's decision levers, and written challenge prompts that provoke the reader to pressure-test the work. Works at ANY scope — from one line of code to the whole project: it SIZES the target into a scope tier, DECOMPOSES a large one into understanding groups, BREAKS the work into tasks before the first deep read, and ACCUMULATES the report group by group on disk so a huge explanation stays complete instead of thinning out. Writes the full report to a single combined markdown file (plans/reports/understand-*.md) that opens with a detailed summary section — or delivers it in full in chat when Step 3 finds no git-ignored directory for it — and always summarizes it in chat. Regardless of coding level. Never interrogates, never quizzes, never blocks.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Use when reviewing rationale and change quality for plans, PBIs, commits, diffs, docs, specs, reports, or explicit artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
[Code Intelligence] Use when you need to export the code review knowledge graph. Flag: --format={json|mermaid} (default json); --format=json dumps the full graph to a JSON file, --format=mermaid renders a single file as a Mermaid flowchart diagram.
日本語の概要は準備中です。原文の説明を表示しています。
[Implementation] Use when you need to start coding & testing an existing plan. Flags: --approval=off (auto/trust mode, no approval gate), --tests=off (skip the test step), --parallel={auto|on|off} (default off — sequential; --parallel/=on opts in to parallel sub-agent waves; =auto fans out only when the plan declares PAR/SEQ tags and write sets).
日本語の概要は準備中です。原文の説明を表示しています。
[Research] Use when you need to review knowledge artifacts for completeness, citation quality, confidence accuracy, and template compliance.
日本語の概要は準備中です。原文の説明を表示しています。
[Project Management] Use when you need to generate an HTML mockup report from PBI and story artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
[Planning] Use when you need to start a new project from scratch with full waterfall inception — idea, research, domain modeling, tech stack, and implementation plan.
日本語の概要は準備中です。原文の説明を表示しています。
[Utilities] Use when you need to save analysis context to a checkpoint file for recovery (user-facing alias for memory-management Part 1 CHECKPOINT_CREATE).
日本語の概要は準備中です。原文の説明を表示しています。
[Fix & Debug] Use when investigating a bug's root cause — reproduce the symptom, trace it end-to-start through the code, form and test hypotheses, and pinpoint the defect before any fix.
日本語の概要は準備中です。原文の説明を表示しています。
Design relational database schemas (and choose when to go NoSQL) that stay maintainable and fast. Use this skill whenever the user mentions tables, DDL, entities and relationships, normalization (1NF/2NF/3NF), primary and foreign keys, UUID vs bigint IDs, indexes (B-tree, composite, covering, partial), EXPLAIN, constraints (CHECK, UNIQUE, exclusion), transactions and isolation levels, migrations (Alembic, Prisma, Flyway, expand-contract, backfilling), or SQL vs NoSQL (MongoDB, DynamoDB, Cassandra, graph databases). Also trigger for "design the database", "model this domain", "which database should I use", or writing ORM models and migration files for PostgreSQL, MySQL, SQLite, or SQL Server.
日本語の概要は準備中です。原文の説明を表示しています。
Builds and improves task-specific decision artifacts from application requirements and labeled records. Use for data assembly, primitive and base-model selection, fitting, export/reload, inference policy, or bounded data/model/program improvement. Includes rules and no-training outcomes; does not require a rung ladder or training a general Jev.
日本語の概要は準備中です。原文の説明を表示しています。
Handles public relations, media outreach, press releases, and earned media strategy for SMEs. Creates press releases, media pitches, spokesperson briefings, crisis communication plans, and event communications. Use when user asks about PR, press releases, media relations, journalist outreach, crisis communication, or public-facing communications.
日本語の概要は準備中です。原文の説明を表示しています。
Manages government affairs, public policy communications, and collective action aligned with B Corp GACA standards. Creates policy position papers, advocacy communications, regulatory response documents, and transparent lobbying reports. Use when user asks about government relations, public policy, advocacy, lobbying, regulatory affairs, collective action, or political engagement transparency.
日本語の概要は準備中です。原文の説明を表示しています。
Creates LinkedIn posts, thought leadership content, and editorial calendars for SME marketing. Covers 7 post types (Awareness, Personal Story, Education, Conversion, How We Do It, Building In Public, Lead Magnet) with complete graphic prompts, first comments, and CTAs. Use when user asks to write social media posts, plan content calendars, create LinkedIn content, or develop thought leadership pieces.
日本語の概要は準備中です。原文の説明を表示しています。
Guides continuous improvement and change management for SMEs adopting AI. Applies Marginal Gains philosophy, Kaizen principles, and structured sprint methodologies to organizational transformation. Use when user asks about change management, continuous improvement, AI adoption strategy, team resistance, transformation roadmaps, or improvement sprints.
日本語の概要は準備中です。原文の説明を表示しています。
Manages brand identity, visual design system, and creative quality for MMIND.ai. Generates complete image prompts for Nano Banana Pro (Gemini), enforces the strict 5-color palette, flat-vector SaaS style, and typography standards. Use when user needs graphic prompts, brand consistency checks, visual style guidance, design briefs, or creative QA for any marketing asset.
日本語の概要は準備中です。原文の説明を表示しています。