bead-workflow
Manage beads correctly including claiming, closing, announcements, and dependencies. Use when starting work on a task, when finishing a task, when the user mentions beads or tasks, or when coordinating with oth...
Discover tools project management skills, compare source repositories and read the instructions for each workflow.
Manage beads correctly including claiming, closing, announcements, and dependencies. Use when starting work on a task, when finishing a task, when the user mentions beads or tasks, or when coordinating with oth...
Data scientist specializing in startup analytics, user behavior tracking, and metrics analysis for Lean Startup and Customer Development methodologies. Use when analyzing user data, setting up analytics, measur...
Troubleshoot ARC (Actions Runner Controller) runners on Rackspace Spot Kubernetes. Diagnose stuck jobs, scaling issues, and cluster access. Activates on "runner", "ARC", "stuck job", "queued", "GitHub Actions",...
Best practices for running GitHub Actions ARC runners on Rackspace Spot Kubernetes. Covers spot instance management, preemption handling, cost optimization, and resilience strategies. Activates on "rackspace sp...
DPPM (Discover, Plan, Prototype, Monitor) planning and orchestration with mandatory plan documents, impact analysis, ASCII diagrams, task breakdowns, evidence gating, context-compaction check-ins, and user test...
Railway deployment management for {{PROJECT_NAME}}: CLI, env vars, health checks, troubleshooting, rollback.
Update Agent Communication Board with task status, completion messages, and blocker tracking. Use after completing tasks or when blocked.
Break complex features into delegatable tasks with clear ownership and dependencies. Use for feature planning phase.
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD che...
Break complex features into delegatable tasks with clear ownership and dependencies. Use for feature planning phase.
Update Agent Communication Board with task status, completion messages, and blocker tracking. Use after completing tasks or when blocked.
Break complex features into delegatable tasks with clear ownership and dependencies. Use for feature planning phase.
Expert in Template Project frontend architecture, React patterns, TypeScript, TanStack Query, Zustand, and component development with strong type safety. Use when building UI components, implementing data fetch...
Expert in Template Project mobile architecture using Expo, React Native, TypeScript, and Zustand. Use when building mobile screens, implementing navigation, managing state, styling components, integrating with...
Use to implement tickets created by writing-tickets skill
Generates comprehensive context summaries for async team handoffs. Use when user says "create handoff", "handoff summary", "I'm leaving for the day", or needs to pass work to another team member.
Deep-dive technical discovery and requirement gathering before coding. Use when a task is broad, ambiguous, or requires architectural decisions.
Generate architecture, sequence, state, and ERD diagrams for code understanding. Use when user wants to visualize code structure or document systems.
Record task metrics after completing work. Use after /verify or any completed task to build measurement data.
Capture task outcomes and patterns after completing work. Use after /verify or when a task succeeds/fails to enable adaptive skill evolution.
Break down tickets or requirements into actionable task checklists. Use when user wants to plan a feature, start a new task, or decompose work before coding.
Use this skill when a file exceeds ~350 lines (target) / approaches the 500-line hard cap, or has mixed responsibilities (UI + Logic + Types).
Maintain a lightweight backlog of high-value tasks discovered during work.
Create and maintain PLANS.md for long-running or risky tasks.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.