Plan & spec
10,807 rows, by stacks then stars
2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid
charlieviettq/awesome-agent-skill/plugins/knowledge-work-product-management/skills/write-spec Skill
24★ repoWrite a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
sidiangongyuan/codex-skills-library/skills/experiment-planner Skill
24★ repoPractical Codex workflows for research, academic writing, app development, general planning, and technical operations.
Paper framework figure studio pro
sidiangongyuan/codex-skills-library/skills/paper-framework-figure-studio-pro Skill
24★ repoUse when planning a source-grounded method overview, architecture, pipeline, system/data-flow, mechanism, or agent-workflow figure for a CS or deep-learning paper. Produces an editable figure brief before image generation or manual redrawing; not for plots, tables, or general prose.
andyzengmath/quantum-loop/skills/ql-execute Skill
24★ repoPart of the quantum-loop autonomous development pipeline (brainstorm \u2192 spec \u2192 plan \u2192 execute \u2192 review \u2192 verify). Run the autonomous execution loop. Reads quantum.json, queries the dependency DAG, implements stories with TDD and two-stage review gates. Supports parallel execution via native worktree isolation. Use after /quantum-loop:plan has created quantum.json. Triggers on: execute, run loop, start building, ql-execute.
andyzengmath/quantum-loop/skills/ql-plan Skill
24★ repoPart of the quantum-loop autonomous development pipeline (brainstorm \u2192 spec \u2192 plan \u2192 execute \u2192 review \u2192 verify). Convert a PRD into machine-readable quantum.json with dependency DAG, granular 2-5 minute tasks, and execution metadata. Use after creating a spec with /quantum-loop:spec. Triggers on: create plan, convert to json, plan tasks, generate quantum json, ql-plan.
andyzengmath/quantum-loop/skills/ql-review Skill
24★ repoPart of the quantum-loop autonomous development pipeline (brainstorm \u2192 spec \u2192 plan \u2192 execute \u2192 review \u2192 verify). Two-stage code review. Spec compliance first, then code quality. Use after implementation or before merge. Triggers on: review code, code review, check implementation, ql-review.
The same file is in 1 other repository
andyzengmath/quantum-loop/skills/ql-spec Skill
24★ repoPart of the quantum-loop autonomous development pipeline (brainstorm \u2192 spec \u2192 plan \u2192 execute \u2192 review \u2192 verify). Generate a structured Product Requirements Document (PRD) with user stories, acceptance criteria, and functional requirements. Use when you have an approved design and need formal requirements, or when starting from scratch. Triggers on: create spec, write prd, spec out, requirements for, ql-spec.
andyzengmath/quantum-loop/skills/ql-verify Skill
24★ repoPart of the quantum-loop autonomous development pipeline (brainstorm \u2192 spec \u2192 plan \u2192 execute \u2192 review \u2192 verify). Iron Law verification gate. Requires fresh evidence before any completion claim. Use before claiming work is done, before committing, or before marking a story as passed. Triggers on: verify, check, prove it works, ql-verify.
Enriching iocs with threat intel sources
meltedinhex/analyst-ai-pack/skills/enriching-iocs-with-threat-intel-sources Skill
24★ repoEnriches indicators with context from threat-intel sources: planning lookups against reputation, passive DNS, WHOIS, and sandbox/sample databases, scoring confidence, and avoiding operational-security mistakes that tip off adversaries. Activates for requests to enrich IOCs, add threat context, or plan indicator lookups safely.
Scoping an incident from a single indicator
meltedinhex/analyst-ai-pack/skills/scoping-an-incident-from-a-single-indicator Skill
24★ repoExpands one indicator into the full scope of an incident: pivoting across data sources to find related hosts, accounts, and infrastructure, building a timeline, and bounding what is and is not affected. Activates for requests to scope an incident, pivot from a single IOC, or determine the blast radius of a detection.
appleboy/skills/plugins/plan-feature/skills/plan-feature Skill
no license23★ repoPlan a feature before writing any code. Use this skill at the START of non-trivial feature work — when the user says they want to "add", "build", "implement", "create", "develop", or "ship" a feature, endpoint, component, page, service, or capability. Especially trigger when the user's prompt is short or under-specified ("add a dashboard", "build an auth flow", "let's do user activity reports") — those need planning, not direct execution. The skill walks through requirements clarification, codebase exploration, sketches a Mermaid architecture/flow diagram of the proposed design, and produces a plan.md document the user can hand off to a fresh AI session for execution. Skip only when the change is genuinely trivial (typo fixes, single-line tweaks, renames). When in doubt, plan.
The same file is in 2 other repositories
joaquimscosta/arkhe-claude-plugins/plugins/core/skills/sdlc-develop Skill
23★ repoOrchestrates 6-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) for guided feature development. Use when user runs /core:develop command, requests spec-driven development, wants to create implementation plans with architecture decisions, or mentions "SDLC", "spec-driven", "plan feature", "development pipeline". Supports plan persistence, wave-based resume, autonomous mode, and architecture/implementation verification.
joaquimscosta/arkhe-claude-plugins/plugins/core/skills/workflow-orchestration Skill
23★ repoCoordinate structured thinking and multi-agent parallel execution for complex tasks. Use when tackling multi-step projects, planning parallel work, breaking down complex problems, coordinating specialist tasks, facing architectural decisions, or when user mentions "workflow", "orchestration", "multi-step", "coordinate", "parallel execution", "structured thinking", "break this down", "plan this out", "how should I approach", or needs help planning complex implementations.
The same file is in 2 other repositories
joaquimscosta/arkhe-claude-plugins/plugins/doc/skills/rfc Skill
23★ repoManage architecture RFCs: create, review, list, update, and transition status. Use when user mentions "RFC", "technical proposal", "architecture proposal", or wants to draft, review, list, update, or change status of RFCs.
The same file is in 2 other repositories
joaquimscosta/arkhe-claude-plugins/plugins/ralph/skills/ralph-prd Skill
23★ repoCreate Product Requirements Document (PRD) and setup for Ralph autonomous loop. Use when user runs /create-prd command, wants to set up a project for Ralph, mentions "ralph setup", "create prd", "product requirements", or needs to generate tasks for autonomous development.
joaquimscosta/arkhe-claude-plugins/plugins/roadmap/skills/pm Skill
23★ repoAnalyze features from user perspective and write user stories with acceptance criteria. Use when defining requirements, writing user stories, validating scope against project state, prioritizing features by impact, comparing approaches, analyzing user needs, or planning next work. Triggers: "user story", "acceptance criteria", "scope", "prioritize", "compare requirements", "user needs", "what to build next".
joaquimscosta/arkhe-claude-plugins/plugins/roadmap/skills/roadmap Skill
23★ repoSynthesize project documentation and codebase into comprehensive roadmap status, gaps analysis, and blockers. Use when assessing project health, identifying blockers, tracking progress, comparing plan vs reality, documenting risks, or planning next milestones. Triggers: "roadmap", "project status", "blockers", "risks", "progress", "next milestone", "gaps", "what's done".
tinh2/skills-hub-registry/analysis/alert-prioritization Skill
no license23★ repoAnalyzes SIEM alert pipelines for rule optimization, alert fatigue reduction, criticality scoring, asset-based prioritization, and correlation rule design using NIST CSF and detection engineering principles. USE THIS SKILL WHEN: - Your SOC team is drowning in alerts and you need to reduce noise - Someone asks about alert fatigue, false positive rates, or SIEM tuning - You need to design or evaluate an alert criticality scoring framework - A project involves SIEM rules (Splunk, Elastic, Sentinel, Chronicle, QRadar) - You are building or reviewing detection-as-code pipelines - Someone mentions MITRE ATT&CK coverage gaps or detection engineering - You need to optimize correlation rules or SOAR playbook coverage - Alert-to-incident conversion rates are below 30% - Analysts are bulk-closing alerts or MTTA is trending upward TRIGGER PHRASES: "alert fatigue", "SIEM tuning", "detection rules", "alert prioritization", "false positive rate", "correlation rules", "SOC optimization", "alert scoring", "detection engineering", "MITRE ATT&CK coverage", "alert volume", "triage optimization"
tinh2/skills-hub-registry/analysis/backend-spec Skill
no license23★ repoGenerates backend or frontend engineering specs in structured Jira format with description, categorized acceptance criteria, routes, dev notes, and table schemas.
tinh2/skills-hub-registry/analysis/care-plan-optimizer Skill
no license23★ repoAnalyze mental health care planning systems for treatment goal alignment, intervention scheduling, progress milestone tracking, multi-provider coordination, step-down/step-up criteria, and individualized care pathway optimization. USE THIS SKILL WHEN: user mentions care plan optimization, treatment planning, mental health software, therapy scheduling, clinical goal tracking, level-of-care transitions, multi-provider coordination, progress milestones, or recovery-oriented care systems. Trigger phrases: "analyze care plan system", "treatment goal alignment review", "intervention scheduling audit", "milestone tracking evaluation", "care coordination review", "step-down criteria analysis", "care pathway optimization", "treatment planning system audit", "multi-provider workflow review".
tinh2/skills-hub-registry/analysis/codebase-migration Skill
no license23★ repoFour-phase skill for planning and executing large-scale codebase migrations using full-context AI analysis. Produces an impact map, ordered batch plan, subagent execution protocol, and cross-codebase validation pass. Optimized for Fable 5's 1M-token context window.
tinh2/skills-hub-registry/analysis/crisis-risk-monitor Skill
no license23★ repoAudit mental health crisis monitoring systems for risk signal detection accuracy, escalation protocol completeness, safety planning integration, crisis team coordination, and ethical guardrail enforcement. Covers PHQ-9/C-SSRS/GAD-7 instrument integration, NLP risk detection in clinical notes, escalation tier workflows, safety plan accessibility and activation, mandatory reporting compliance, consent management, and algorithmic fairness in risk scoring. Use when reviewing behavioral health platforms, telehealth systems, EHR crisis modules, crisis hotline software, or any system that detects and responds to mental health risk signals.
tinh2/skills-hub-registry/analysis/extraction-optimization Skill
no license23★ repoOptimize mining extraction operations by analyzing ore grade control, processing plant throughput, metallurgical recovery rates, energy consumption, and water balance. Covers mine-to-mill reconciliation, comminution circuit tuning, flotation and leach kinetics, cut-off grade strategy, OEE analysis, and produces a prioritized improvement roadmap for mine operations teams.
tinh2/skills-hub-registry/analysis/requirements-verification Skill
no license23★ repoAutonomous requirements analysis agent. Parses a spec file (SPEC.md, requirements doc, or any plain-text specification) and runs a structured pass to surface logical contradictions, ambiguous requirements, and underdefined gaps — before any implementation begins. Inspired by Kiro's neurosymbolic Requirements Analysis engine (May 2026). Reports issues as structured, actionable resolution choices.
tinh2/skills-hub-registry/analysis/resource-estimation Skill
no license23★ repoAudit a mineral resource estimation system -- evaluate drillhole database integrity and QA/QC (CRMs, blanks, duplicates, umpire checks), geological and domain modeling quality, variogram analysis and grade interpolation methods (ordinary kriging, indicator kriging, IDW, conditional simulation), resource classification criteria (Measured, Indicated, Inferred), economic cut-off grade calculation, reserve conversion with modifying factors, pit/stope optimization, and depletion reconciliation. Reports against JORC 2012, NI 43-101, CIM 2014, SAMREC, S-K 1300, and PERC codes for any commodity (Au, Cu, Fe, Li, REE, coal).
tinh2/skills-hub-registry/analysis/seo-content-brief Skill
no license23★ repoGenerate a 2026-grade content brief for a target query — combines classic SERP analysis with AI Overview / Perplexity / ChatGPT citation analysis, entity recommendations (target ≥15 recognized entities), topical authority gap map, intent-mapped heading structure, internal linking targets, FAQ from PAA + Reddit + AI prompt mining, and explicit E-E-A-T requirements (author entity profile, first-party data needed, primary source citations). Replaces older keyword-density-focused briefs. The brief tells a writer EXACTLY what to include for both Google ranking AND AI citation. TRIGGER on "content brief", "SEO brief", "article outline", "blog post brief", "topic outline", "write a brief for [keyword]", "content strategy for [topic]", "what should we write about [X]". Skip if user just wants a content idea — this skill is for the page-level brief, not the editorial calendar.
tinh2/skills-hub-registry/build/kiro-spec-driven Skill
no license23★ repoSpec-driven development agent for AWS Kiro. Captures feature requirements, generates EARS-notation specifications, produces architectural designs, sequences implementation tasks, and validates the final code against the spec checklist. Use when you want rigorous, maintainable feature builds instead of vibe-coded prototypes.
tinh2/skills-hub-registry/combo/mvp-spec Skill
no license23★ repoChains /mvp → /spec — analyzes an app from video/screenshots/description, then generates implementation stories. Triggers: analyze and spec, product analysis to stories, app teardown to specs, full analysis pipeline, mvp to spec.
tinh2/skills-hub-registry/combo/spec Skill
no license23★ repoChains /mvp → /backend-spec — analyzes an app from video/screenshots/description, then generates implementation stories from the analysis.
tinh2/skills-hub-registry/docs/backend-spec Skill
no license23★ repoGenerates structured engineering specs (backend or frontend) from feature descriptions, designs, or ticket references. Triggers on "spec", "story", "ticket", "engineering spec", "write a story for", "write a spec for", "create a ticket for".
tinh2/skills-hub-registry/productivity/kiro-quick-plan Skill
no license23★ repoFast single-pass spec-and-execute loop that mirrors Kiro 0.12's Quick Plan Mode. Generates requirements, design, and task list in one pass (no approval gates), then executes tasks in parallel where dependencies allow. Use when you want spec-driven rigor without the three-gate approval workflow — spikes, small features, or well-understood tasks where speed beats review overhead.
tinh2/skills-hub-registry/productivity/plan-to-issues Skill
no license23★ repoConvert a plan, PRD, spec, or roadmap document into tracked GitHub issues with a dependency graph: parses the plan into atomic work items (each independently shippable, one day or less, with acceptance criteria), detects dependency cycles before creating anything, then uses the gh CLI to create a milestone, type and priority labels, and issues whose bodies carry context, acceptance criteria, likely-touched files, and depends-on links created in topological order so references resolve. Verifies the created set and emits a plan-item to issue-URL mapping table. Use when the user says: turn this plan into issues, create GitHub issues from this PRD, break this spec into tickets, file issues for this roadmap, to-issues, convert plan to tasks, issue-ify this, populate the milestone.
tinh2/skills-hub-registry/qa/stress-test-personas Skill
no license23★ repoStress-test your product through 6 adversarial decision-maker personas -- skeptical board member, activist investor, power user, churned customer, competitor CEO, and enterprise procurement officer. Each persona attacks from a different strategic angle with findings grounded in actual code references. Use when you need to red-team a product, challenge business viability, find competitive weaknesses, evaluate enterprise readiness, identify churn risks, or pressure-test product strategy before a launch or fundraise.
tinh2/skills-hub-registry/review/cto-review Skill
no license23★ repoConduct a CTO-perspective technical strategy review of a codebase. Evaluates architecture decisions and build-vs-buy trade-offs, scaling readiness at 10x and 100x, engineering velocity and developer experience, technical debt ratio and blast radius, security posture at executive level, team scalability for hiring, and infrastructure cost efficiency. Produces a strategic risk matrix, architecture scorecard, and ranked investment priorities. Use when you need a technical strategy review, architecture assessment, scaling readiness check, tech debt audit, engineering velocity evaluation, Series A technical due diligence, or CTO-level briefing before a board meeting or fundraise.
tinh2/skills-hub-registry/spec/design-spec Skill
no license23★ repoLock down design decisions before implementation — app name, terminology, design tokens, screen inventory, data models, and microcopy. Outputs a design-spec.md that other skills reference.
tinh2/skills-hub-registry/spec/idea-to-prd Skill
no license23★ repoTurns a raw idea, brain dump, or conversation into a complete PRD with mandatory acceptance criteria and measurable success metrics. Extracts the problem, target users, and jobs-to-be-done, runs a quick competitive scan (web if available, logged as a gap if not), drafts the full PRD (problem, personas, user stories with testable acceptance criteria, non-goals, success metrics, launch milestones, open questions, and a distribution section answering how people will find this), then self-critiques against a 10-point rubric and patches gaps before writing docs/prd/<slug>.md. Use when you hear: write a PRD, turn this idea into a spec, product requirements, I have an app idea, formalize this feature, from idea to document, what should the requirements be, draft the product doc, PRD for X, spec out this product, capture this brainstorm.
tinh2/skills-hub-registry/spec/plan-interrogator Skill
no license23★ repoInterrogates a plan or feature idea until zero ambiguity remains, then persists a decision record. Enumerates every unstated assumption, asks prioritized question batches (blocking, then shaping, then polish, multiple-choice where possible), runs an adversarial pass attacking the plan for edge cases, failure modes, and hidden scope, and emits docs/decisions/<date>-<topic>.md with a decisions table, risk register, and explicit non-goals. Use when you hear: grill me on this plan, interrogate this idea, poke holes in my plan, stress-test this feature, what am I missing, challenge my assumptions, is this plan ready, pre-mortem, devil's advocate review, decision record, ADR for this feature, before I start building, make sure the spec is airtight.
tinh2/skills-hub-registry/test/manual-test-plan Skill
no license23★ repoGenerates a manual test plan, QA plan, test scenarios, testing checklist, or guidance on how to test changes. Works from branch diffs, stories, specs, or requirements.
gtrabanco/agentic-workflow/skills/design-feature Skill
23★ repoTurn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
gtrabanco/agentic-workflow/skills/plan-feature-from-issue Skill
23★ repoInternal step of plan-feature: turn a feature-request issue into a scoped, sized, roadmap-mapped SPEC **product half** (capability closure satisfied) with Closes #N traceability.
gtrabanco/agentic-workflow/skills/plan-feature-scaffold Skill
23★ repoInternal step of plan-feature: from an already-designed SPEC (product half `designed`), fill the **engineering half** and generate the planning artifact set scaled to the feature's size (XS/S → SPEC-only with ≥ 2 phases in the SPEC, last = Hardening & PR; M/L → full set with a hardening phase), freeze one compact ACCEPTANCE.md for every size, and register the roadmap entry. Docs only — never code.
gtrabanco/agentic-workflow/skills/plan-feature Skill
23★ repoRoute designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports `--next`, `--from-issue`, and `--scaffold`. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
gtrabanco/agentic-workflow/skills/plan-fix Skill
23★ repoDraft and locally commit a tightly scoped, phased fix SPEC from one or more issues, then stop before push/PR and hand off to execute-phase --fix. Triggers: "plan-fix", "plan a fix for issue N", "draft the fix spec".
gtrabanco/agentic-workflow/skills/ship-roadmap Skill
23★ repoFound or continue a roadmap autopilot one stage per invocation. Default: human merge. --fullauto is invocation-scoped and uses the transient wrapper only after a fresh audit. Triggers: "ship-roadmap", "ship the roadmap", "autopilot this project".
Xuxchloris/export_skills/skills/follow-up-planner Skill
23★ repoUse when a trade agent needs outreach follow-up timing, next-touch planning, reminder schedules, buyer reply follow-up, quotation follow-up, sample follow-up, or prospect status updates
alexclowe/awesome-copilot-cowork-plugins/construction-pm/skills/stakeholder-communication Skill
23★ repoOwner reports, subcontractor coordination, RFI responses, and meeting documentation
alexclowe/awesome-copilot-cowork-plugins/financial-advisor/skills/financial-planning Skill
23★ repoFinancial planning knowledge for retirement, education, estate, tax, and insurance needs analysis
alexclowe/awesome-copilot-cowork-plugins/interior-designer/skills/interior-design Skill
23★ repoInterior design expertise for space planning, material specification, and design documentation
alexclowe/awesome-copilot-cowork-plugins/management-consultant/skills/strategic-analysis Skill
23★ repoManagement consulting frameworks, structured problem-solving, and analytical thinking
alexclowe/awesome-copilot-cowork-plugins/sales-rep/skills/sales-strategy Skill
23★ repoConsultative selling, MEDDIC/BANT frameworks, value-based positioning, objection handling, and pipeline management
alexclowe/awesome-copilot-cowork-plugins/social-media-manager/skills/visual-design-brief Skill
23★ repoDesigner-ready visual brief expertise — layout, palette, type, mood, and motion notes for handoff to Claude Design or a designer
lionkiii/claude-seo-skills/skills/seo-content-brief Skill
22★ repoGenerate a structured SEO content brief for a keyword using live Ahrefs SERP data and optional GSC overlay. Use when user says "content brief", "write a brief for", "content plan for keyword", "what should I write about", "brief for article", "content strategy for keyword", "help me write content for", or "create a brief for".
lionkiii/claude-seo-skills/skills/seo-plan Skill
22★ repoStrategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content strategy", "site architecture", "SEO roadmap", "keyword strategy", "content calendar", "site architecture plan", "SEO budget", or "SEO timeline".
NintendaDev/unikit-ai/skills/unikit-devcontext Skill
22★ repoSenior {{engine_name}}/{{engine_code_language}} developer that performs direct, ad-hoc code tasks without a formal plan — and the code-execution engine other unikit skills and agents delegate to. Use it whenever the user asks to do something in code right now, e.g. "add this method to this class", "refactor this function", "write a script that does X", "change this code", "optimize this class". Phrases like "without a plan", "no plan", "just do it", or "directly" are strong signals to use this skill rather than planning. Covers writing, refactoring, optimizing, and discussing {{engine_code_language}} code and patterns (DI, ECS, MVC, state machines, event systems). For a larger multi-step feature, plan it with /unikit-plan and build it with /unikit-implement — this skill is for direct, unplanned code work.
NintendaDev/unikit-ai/skills/unikit-gd-explore Skill
22★ repoResearch and ideation partner for GAME DESIGN — think through design ideas before writing them into the GDD; produces a brief, never edits the GDD itself. Use to assess a genre or market for viability, dissect a reference game (mechanics → dynamics → aesthetics), explore how to improve or extend an existing system, flow, or content type, research new mechanics the design lacks, investigate a part of the GDD in code, or develop the research bucket of a /unikit-gd-review report into decided edits. Trigger on "explore how to improve the flow", "ways to improve the combat system", "is this genre saturated", "break down the combat of Hades", "work out the review's open questions". GAME-DESIGN research only — for CODE or technical research use /unikit-explore; to reconstruct a design from code use /unikit-gd-recon; to write a change into the GDD use /unikit-gd-system or /unikit-gd-spec; to apply edits you know use /unikit-gd-apply; to invent a new game use /unikit-gd-brainstorm.
NintendaDev/unikit-ai/skills/unikit-gd-spec Skill
22★ repoCreate and own the master game design document (GAME.md — the authored one-pager plus the generated [gen] system/flow maps) and the GD-IDS.yaml facts registry — the top-level, big-picture layer of the GDD and the machine interface the code side reads. Use it to write the master spec from a concept or dialogue, import an existing GDD (a file path or URL), edit GAME.md content ("change a pillar", "rework the monetization stance", "tweak the loop stack"), pitch the game ("pitch" → PITCH.md), re-decompose the systems ("remap"), and — importantly — to add a new system to the design map ("let's add a new system", "add a crafting system to the game design", "add this to the GDD"). This is the structural, map-level layer plus GAME.md content edits. To write or fill in the detailed parameters of one existing system, use /unikit-gd-system; to apply one edit spanning several zones at once use /unikit-gd-apply; to invent a brand-new game concept use /unikit-gd-brainstorm.
NintendaDev/unikit-ai/skills/unikit-help Skill
22★ repoNavigator and help guide for the UniKit framework — use when the user is unsure what to do next, where to start, or which unikit skill fits their situation. It diagnoses intent and points to the right skill or pipeline: starting a project, writing code, testing, planning, the spec-driven code workflow, authoring or detailing game design, finding a new mechanic, or deciding what game to build. Trigger on questions like "what do I do next", "where do I start", "how do I start coding", "how do I test my code", "how do I create the game design", "how do I detail a system", "how do I find a new mechanic", "which unikit skill should I use", "how does the code pipeline relate to game design", "I'm lost in unikit", "help me with unikit". Read-only — it explains and points to the right command, it never edits project files. For technical code research use /unikit-explore; for game-design research use /unikit-gd-explore; to initialize the framework use /unikit.
NintendaDev/unikit-ai/skills/unikit-implement Skill
22★ repoExecute the tasks from an already-created feature plan in .unikit/code/plans/ — read the plan (TASKS.md + PLAN-BRIEF.md), 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.
NintendaDev/unikit-ai/skills/unikit-plan Skill
22★ repoCreate an implementation plan for a feature — a dependency-ordered, actionable task list for the project. Has three modes: fast (a quick single-pass plan), full (a richer plan that can also create a git branch), and add (extend an existing plan with more tasks). Pick the mode from the user's wording: "full plan" runs full; "quick plan" or "fast plan" runs fast; a plain "create a plan" with no qualifier defaults to fast; "add to the plan" or "extend the plan" runs add. Use whenever the user wants to plan a feature or task, e.g. "create a plan", "create a full plan", "create a quick plan", "plan this feature", "just plan this", "add this to the plan", "extend the plan", "add a phase to the plan".
NintendaDev/unikit-ai/skills/unikit-roadmap Skill
22★ repoCreate or update a strategic project roadmap with major milestones. Generates .unikit/ROADMAP.md — a high-level checklist of project goals. Use when user says "roadmap", "project plan", "milestones", "what to build next", "strategic goals", or wants to see big-picture progress. Also use when the user asks to check which milestones are done or wants to plan the overall project direction.