Skills tagged planning: 49 agent skills for Claude Code
architect — Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
autoplan — Auto-review pipeline — reads the full CEO, design, eng.
claude-code-ping-start-5h-quota — 睡前/离开前额度耗尽时，设置一次性本机定时器，在 Claude 订阅额度重置后自动发一条极简 claude -p 消息，立刻开启新的 5 小时用量窗口——用户睡醒时新窗口已跑掉大半，等于白赚一个 冷却期。Use when 用户说「还有 X 小时重置额度，帮我定时戳一下 Claude」「我去睡觉了， 到点 ping.
claude-md-progressive-disclosurer — Optimize, slim, or restructure CLAUDE.md/AGENTS.md with progressive disclosure and zero information loss. Use when the user explicitly asks to audit, 精简, 瘦身.
cloudflare-one-migrations — Assess and plan migrations from existing VPN, SWG, or SASE platforms to Cloudflare One, including policy mapping, parity gaps, and rollout.
co-marketing — When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities.
content-strategy — When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover.
create-learning-path — Build a personalized learning roadmap with milestones and practice checkpoints
events — When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops.
expo-overview — Framework (OSS). Entry point and router for every Expo or EAS task.
figure-it-out — Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away.
grill-with-docs — A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
gstack-openclaw-ceo-review — Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope.
i-have-adhd — Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents.
improve-animations — Survey a codebase's animation and motion code as a senior motion advisor.
launch — When the user wants to plan a product launch, feature announcement, or release strategy.
lean-build — Build feature work with high overbuilding risk.
llm-wiki-setup — Co-create a personal investment-research LLM Wiki (Andrej Karpathy's pattern) where the user's OWN analysis framework becomes a living CLAUDE.md — by.
loop-me — Grill me about specs for the workflows I want to build, within this workspace.
marketing-ideas — When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.
marketing-loops — When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily.
marketing-plan — When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
new-unity-project — Use when starting a brand-new Unity game or project from scratch — "make/start/create a new game", "bootstrap a Unity project".
orchestrate — Use only when the user explicitly types `/orchestrate <goal>` to decompose a large task.
pick-ui-library — Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop.
planner — Generate staged project plans from design through deployment.
principle-foundational-thinking — Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share.
principle-sequence-verifiable-units — Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs.
product-marketing — When the user wants to create or update their product marketing context document.
public-relations — When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).
resilience-program-design — Designs a resilience program: how to structure and standardize resilience policies across an organization, team.
run-learning-retrospective — Evaluate learning progress, identify blockers, and adjust the learning plan
seo-cluster — SERP-based semantic topic clustering for content architecture planning.
seo-content-brief — Generate competitive SEO content briefs with per-section word counts, competitor scoring, keyword density guidance, and page-type templates.
seo-flow — FLOW framework integration: evidence-led SEO using the Find → Leverage → Optimize → Win loop.
seo-plan — Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap.
site-architecture — When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
spec — Turn vague intent into a precise, executable spec in five phases. (gstack)
to-questionnaire — Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
to-spec — Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
to-tickets — Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges.
wayfinder — Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker.
weekly-review — Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work