Loading...
Loading...
Found 56 Skills
Advanced Scrum Master with data-driven team health analysis, velocity forecasting, retrospective insights, and team development expertise. Features comprehensive sprint health scoring, Monte Carlo forecasting, and psychological safety frameworks for high-performing agile teams.
Generates a detailed project explanation and retrospective (FOR_USER.md) to help the user learn from the project. Use this skill when the user asks to explain the project, asks "what did we just build?", or invokes the skill to generate a learning resource after a coding session.
After an agentic task completes, perform a retrospective analysis across 6 dimensions (goal alignment, efficiency, decision quality, error handling, communication, reusability). Score performance, identify inefficiency patterns, evaluate skill usage, and produce actionable improvement recommendations. Triggers on "how did it go", "retrospective", "review performance", "what could be better", or after any long agentic task completes.
Structured session analysis and project instruction refinement using a five-type intervention taxonomy (Correction, Repetition, Role Redirect, Frustration Escalation, Workaround) with severity scoring to categorize process gaps. Refines project instructions (CLAUDE.md, AGENTS.md, .team/coordinator-instructions.md) with structural (not advisory) language, maintains WORKING_STATE.md for crash recovery (read-first-after-any- interruption protocol), and implements a self-reminder protocol (re-read constraints every 5-10 messages to prevent role drift). Includes advisory- to-structural promotion pattern for recurring gaps. Activate after milestones, repeated user corrections, session restarts, crash recovery, every 5 completed tasks, or on user request. Triggers on: "reflect on this session", "why do I keep correcting you", "update project instructions", "update working state", "session retrospective", "crash recovery", "context compaction", "role drift", "I keep telling you the same thing", "analyze my corrections". Also relevant when the agent notices repeated corrections, needs to resume after compaction, or wants to prevent known failure modes from recurring.
MindOS Knowledge Base Operation Guide (Chinese) for Agent tasks on local markdown/csv knowledge bases. It should be automatically triggered whenever tasks involve note files, SOP/workflow documents, profile/context documents, CSV tables, knowledge base organization, cross-Agent handover or decision synchronization, and are executed via the MindOS MCP tool. Typical requests include "update notes", "search knowledge base", "organize files", "execute SOP", "review according to team standards", "hand over tasks to another Agent", "synchronize decisions", "append to CSV", "retrospect this conversation", "extract key experiences", "adaptively update retrospective results to corresponding documents", "route this information to corresponding files", "synchronously update all related documents", etc.; it should be triggered even if the user does not explicitly mention MindOS.
Turn recent work into an engineering retro with shipped work, patterns, and momentum in one place. Use when asked to "weekly retro", "what did we ship", "engineering retrospective", "retro this sprint", or "team retro". Proactively suggest at the end of a work week or sprint. Requires One Horizon MCP.
BMad Autonomous Development — orchestrates parallel story implementation pipelines. Builds a dependency graph, updates PR status from GitHub, picks stories from the backlog, and runs each through create → dev → review → PR in parallel — each story isolated in its own git worktree — using dedicated subagents with fresh context windows. Loops through the entire sprint plan in batches, with optional epic retrospective. Use when the user says "run BAD", "start autonomous development", "automate the sprint", "run the pipeline", "kick off the sprint", or "start the dev pipeline". Run /bad setup or /bad configure to install and configure the module.
Analyzes git commits and changes within a timeframe or commit range, providing structured summaries for code review, retrospectives, work logs, or session documentation.
Session retrospective and codification. Run at the end of any significant session to extract learnings, update documentation, and create artifacts that make future sessions smoother. Invoke when: - Finishing a multi-step implementation - After debugging a hard problem - End of any session with 3+ tool calls - "what did we learn?" / "wrap up" / "done" Subsumes /codify-learning (codification is one output, not the only one).
Scrum framework fundamentals and sprint goal writing. Covers sprint planning, sprint goals, daily scrums, sprint reviews, retrospectives, scrum roles, artifacts, and goal-writing templates (SMART, FOCUS, FAB). Use when planning sprints, writing sprint goals, or facilitating scrum events.
(Industry standard: Loop Agent / Single Agent) Primary Use Case: Self-contained research, content generation, and exploration where no inner delegation is required. Self-directed research and knowledge capture loop. Use when: starting a session (Orientation), performing research (Synthesis), or closing a session (Seal, Persist, Retrospective). Ensures knowledge survives across isolated agent sessions.
Use this skill when the user wants to debug, diagnose, or systematically iterate on an experiment that already exists, or when they need a structured experiment log for tracking runs, hypotheses, failures, results, and next steps during active research. Apply it to underperforming methods, training that will not converge, regressions after a change, inconsistent results across datasets, aimless experimentation without progress, and questions like 'why doesn't this work?', 'no progress after many attempts', or 'how should I investigate this failure?'. Also use it for setting up practical experiment logging/record-keeping that supports debugging and iteration. Do not use it for designing a brand-new experiment pipeline or full experiment program (use experiment-pipeline), generating research ideas, fixing isolated coding/syntax errors, or writing retrospective summaries into research memory/notes/knowledge bases.