Planning

write-a-prd helps turn a vague feature idea into a GitHub-issue-ready PRD through repo exploration, relentless user interviews, and module design. Best for Requirements Planning in an existing codebase.

ubiquitous-language turns domain conversations into a DDD-style glossary, flags ambiguity and synonyms, proposes canonical terms, and writes `UBIQUITOUS_LANGUAGE.md`. Useful for terminology alignment across docs, APIs, product language, and ubiquitous-language for Technical Writing.

request-refactor-plan helps agents turn a vague refactor idea into a scoped GitHub issue through user interview, repo inspection, option analysis, testing checks, and tiny commit planning.

prd-to-plan turns a PRD into a phased implementation plan using tracer-bullet vertical slices. It guides repo exploration, captures durable architecture decisions, and saves the final Markdown plan in ./plans/ for Requirements Planning.

design-an-interface helps you design module and API surfaces by gathering requirements, generating 3+ radically different options, and comparing tradeoffs before implementation.

The professional-communication skill helps agents draft clearer workplace emails, chat messages, status updates, meeting agendas, and summaries for software teams. It includes What-Why-How structure, audience adaptation, jargon simplification, and remote async communication guidance.

frontend-to-backend-requirements helps frontend teams write backend handoff docs that capture UI data needs, user actions, states, business rules, and open questions without prescribing endpoints or API structure.

difficult-workplace-conversations gives agents a structured Preparation → Delivery → Follow-up framework for feedback, conflict, performance issues, and other tense workplace discussions. Use it to prepare facts, draft opening lines, handle defensiveness, and plan follow-up with the included reference files.

database-schema-designer helps developers and database engineers design production-ready SQL or NoSQL schemas with normalization, indexing, constraints, and migration planning. Includes trigger phrases, a schema design checklist, and a migration template for practical schema generation and review.

daily-meeting-update is an interactive meeting-prep skill that gathers context from GitHub, Git, Jira, and Claude Code history, runs a 4-part interview on yesterday, today, blockers, and discussion topics, then generates a shareable Markdown standup update.

qa-test-planner is an explicit-trigger QA skill for creating test plans, manual test cases, regression suites, Figma design validation notes, and structured bug reports from feature or release context.

The jira skill helps agents handle Jira issue tracking with plain-English requests. It detects whether the jira CLI or Atlassian MCP is available, then supports viewing tickets, listing assigned work, creating issues, adding comments, assigning tickets, and moving items through workflow states.

gepetto is a structured planning skill that turns a markdown spec into researched, sectionized implementation plans through interviews, synthesis, external review, and file-based outputs. Best for Requirements Planning on complex features rather than quick code tasks.

game-changing-features is a product strategy skill for finding 10x opportunities, ranking high-leverage bets, and turning top ideas into Requirements Planning inputs. Best for PMs and founders who need sharper prioritization, clear constraints, and a structured workflow instead of generic feature brainstorming.

prd-to-issues turns a PRD into small, demoable GitHub issues using vertical slices. It helps founders, engineers, and agents fetch a PRD issue, inspect the codebase if needed, label slices as AFK or HITL, and review blockers before creating tickets.