Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Transforms rough requirements into well-structured GitHub issues. Use when the user provides a vague idea, feature request, or problem description and wants to create a GitHub issue. Analyzes codebase, explores solution approaches, researches relevant libraries, and generates actionable issues using `gh` CLI.
Break a big feature into a phased implementation plan with starter prompts, progress tracking, and cross-session state. Opus 4.8 native - each phase runs as its own session with context-saving subagents, agent teams, and (for batch-heavy work) deterministic Workflows, plus a web-research pass for any third-party surface. Use when a feature is too large for one session.
Create a GitHub issue for World of ClaudeCraft in the maintainer's house format. Use when asked to file, open, or create a GitHub issue or bug report from a description, a screenshot, or a rough placeholder. Rewrites the input into a clean, professional issue (Problem, Steps to reproduce, Expected, Actual, Scope, Acceptance criteria) and includes a Screenshot section only for UI/UX issues. Posts to levy-street/world-of-claudecraft via gh.
Invoke when the user asks to "check history", "recall context", "what did we work on", "load prior context", "what's the background on X", "remind me where we left off", or any similar request to surface prior session work. Also invoke proactively at the start of a session continuation when the user references past work that isn't fully described in the current conversation. Uses observation history, context-mode index, and memory files to reconstruct relevant prior state.
Check release readiness and record a release note. Use for release and rollback requests.
Use for concise business travel plans that combine policy constraints, local route facts, and traveler priorities.
Interact with Paca project management using MCP tools. Use when tracking tasks, writing docs, planning sprints, managing work items, creating bugs or features, viewing the board, or handling any project-management request involving Paca. Routes to specialized skills for complex workflows like epics, sprint planning, and task execution.
Break a large Paca task or epic into smaller, actionable sub-tasks with dependency ordering. Use when decomposing work that is too large to estimate or execute in a single session, when creating an implementation plan, or when a task needs to be split into vertical slices before sprint planning.
Clarify a vague or incomplete Paca task or specification by identifying ambiguities, asking targeted questions, and rewriting the description with explicit acceptance criteria. Use when a task is unclear, missing edge cases, lacks a testable done condition, or when someone asks to improve or flesh out a spec.