Discover content media project management skills, compare source repositories and read the instructions for each workflow.
Framework for managing project file context after retros/planning. Trigger after weekly retro + planning complete, after monthly retro + planning complete, or when context feels bloated. Also triggers with "con...
Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes. Triggers on keywords like "analyze plan", "implementation plan", "...
Use when analyzing and improving performance for database queries, API endpoints, or frontend rendering.
Manage Model Context Protocol (MCP) servers - discover, analyze, and execute tools/prompts/resources from configured MCP servers. Use when working with MCP integrations, need to discover available MCP capabilit...
Generate comprehensive work summaries from daily notes or conversation context. Use for performance reviews, project retrospectives, or documenting completed work with timeline and impact.
Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (...
Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
Use when planning parallel execution of independent tasks via subagents or concurrent tool calls; for workflow planning or throughput optimization.
Code implementation expert. Follows the Design-Driven Development lifecycle to execute implementation plans.
Use this skill when requested to commit changes. It ensures commit messages follow project standards, follows the operational policy for character encoding (escaping backticks), and ensures code quality via ver...
Use when encountering bugs, test failures, unexpected behavior, or performance issues before proposing fixes.
Structured problem-solving methodology. Activates for planning, design, debugging, or complex multi-step tasks. Use for systematic analysis and evidence-based reasoning.
Systematic analysis and reasoning workflows. Use when performing audits, investigation, requirements analysis, risk analysis, scenario/edge-case enumeration, or design analysis that demands evidence-based, comp...
Break a problem into atomic, testable subproblems. Use when facing complex tasks, unclear requirements, or planning implementation strategy.
Use when receiving code review feedback before implementing suggestions, especially if unclear or questionable.
TODO list discipline for task tracking. Activates for multi-step tasks (3+), complex work, or when systematic organization is needed. Use for tracking progress and ensuring completeness.
Use when user provides a list of Linear issue IDs to fix sequentially; enforce status transitions (In Progress -> In Review), one issue at a time, and report build/test confirmation strategy.
MUST use for any non-trivial development task in advent-pdp11 - implements iterative development with status tracking, session logging, validation, and one-task-at-a-time approach. Use when implementing feature...
Use this skill when the user expresses ANY intent related to issue/thread management: - Switching issues: "let's work on X", "switch to #Y", "go to the auth issue" - Checking status: "what are we working on?",...
Work management system replacing built-in todos with tracked tasks and stacked changes
This skill should be used when the user asks to "track work across sessions", "create an epic", "manage issue waves", "post a checkpoint", "claim an issue", "recover from compaction", "coordinate multiple agent...
SPC (Single Person Company) AI Team workflow skill. Orchestrates 6 specialized agents (PM, Architect, Designer, Developer, QA, Writer) for full product development lifecycle.
Define, track, and review OKRs with Antigravity-first planning.
Repository structure and dependency analysis for understanding a codebase's architecture. Use when needing to (1) generate a file tree or structure map, (2) analyze import/dependency graphs, (3) identify entry...
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.