create-beads
Use when you have a design or requirements and need to create beads (epics/tasks) for implementation
Use when you have a design or requirements and need to create beads (epics/tasks) for implementation
Summarize the past week's daily journal entries. Use when asked to "weekly review", "review the week", "summarize this week", or "week summary".
Standard Operating Procedure for /tasks phase. Covers task sizing, acceptance criteria definition, and TDD-first task sequencing.
Reports implementation status of project components with evidence. Use when asked about what's done, in progress, or planned for a project.
bmorphism's GitHub stars (2155 repos) and created repos - a curated index of applied category theory, MCP servers, and xenomodern tooling.
Hybrid task decomposition strategy for teamwork projects. Covers plan-based and semantic decomposition, granularity rules, role assignment, and complexity assessment.
Start fresh with cleared history after task completion. Use PROACTIVELY when user says "done"/"finished", all tasks complete, or starting new unrelated work. Clears all history.
ADHD-optimized task tracking with abandonment detection, intervention strategies, and completion accountability
Use when reviewing design documents, technical specifications, or architecture docs before implementation planning
Saves complete session state to STATUS.json for seamless continuation across conversations. Captures git context, in-progress tasks, service status, focus area, and next actions. Use at the end of work sessions, before context limits, or when switching to a different task. Do NOT use mid-task or for quick questions - the overhead is only worthwhile when you actually need to resume later.
Create feature implementation plans before development. Captures requirements, acceptance criteria, non-goals, risks, and implementation complexity in structured markdown. Use when starting a new feature to ensure scope clarity and implementation guidance.
Get GitHub user profile information including repos, followers, and activity. Use when the user asks for GitHub user details, profile information, or developer stats.
Use when you have a written implementation plan to execute
Enterprise Skill for advanced development
Generate resident schedules respecting ACGME rules, institutional policies, and individual preferences. Orchestrates constraint propagation, optimization, and conflict resolution for medical residency program scheduling.
Use when exiting plan mode - where to save implementation plans
Prepare for meetings by gathering context and creating comprehensive agendas
Use this skill when discussing features, planning work, or when users describe what they want to build. Guides MVP thinking - focusing on "what's the minimum to make this work?" rather than comprehensive solutions. Triggers on phrases like "help me think through this feature", "what should we build first?", "how should we scope this?", or any feature planning discussion.
Enterprise Skill for advanced development
SUB-AGENT ONLY: This skill should be used when spawned for read-only research - generates report file and outputs [AGENT_DONE] marker.
This skill should be used when agents need to reset a teamwork project's execution state while preserving metadata. Use before starting a new project in the same session, after a failed project, or when task/verification state is corrupted. Cleans tasks/, verification/, workers/ directories while keeping project.json intact.
Standard Operating Procedure for /implement phase. TDD workflow, anti-duplication checks, task execution, and continuous testing.