Loading...
Loading...
Found 49 Skills
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.
Analyze git commits within a specified time range and generate a work retrospective report. Trigger words: retrospective, review commits, git review, what did I do today, work summary, daily review, retrospective
Skills retrospective and improvement. Use when: - User asks to "review", "retrospect", "summarize" or "复盘" skills - User wants to analyze skills issues from the conversation - User requests skills optimization or improvement - End of conversation or after significant skill usage
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.
Use this tool when you are completing project work and need to extract reusable knowledge from project notes. It is triggered by commands such as "organize assets", "refine", during project retrospectives, or in high-context debugging sessions that reveal valuable patterns. Trigger commands: /asset-refine, /asset-extract
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.
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.
Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control. This skill should be used when the user asks to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wants guided step-by-step development assistance. Platform-agnostic git-only workflow without PR integration. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, merge, standup, retrospective, git.
Orchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
Structures the human review experience for factory-mode builds. Audit trail summaries, PR digests, retrospective synthesis, quality trend tracking, and autonomy tuning interface. Activate during Phase 3 human review.
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.