planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user me...
Découvrez les skills tools project management, comparez leurs dépôts et consultez leurs instructions.
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user me...
Self-improvement workflow after fixing any bug. Analyzes root causes and updates project guidance (CLAUDE.md, skills, commands) to prevent similar bugs. MUST be invoked after completing any bug fix before marki...
Guide for designing Run resources in OptAIC. Use when creating PipelineRun, ExperimentRun, BacktestRun, PortfolioOptimizationRun, TrainingRun, InferenceRun, or MonitoringRun. Covers execution tracking, metrics,...
This skill should be used when the user asks about "spec methodology", "specification workflow", "spec-driven development", "how to write specs", "spec best practices", "specification templates", or needs guida...
Business moderator for backlog prioritization debates. Synthesizes Champion and Critic views into final rankings. Optimizes for team productivity and sustainable velocity.
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
Estimate issue complexity before implementation to prevent timeouts. Uses cheap estimation to save expensive implementation tokens.
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
Design fix plans based on root cause analysis. Use after root cause is identified to plan specific code changes and test cases needed to fix the bug.
Analyze implementation failures and generate recovery plans. Use when an issue fails and needs diagnosis for retry or escalation.
Apply critic feedback to improve an engineering spec. Use when revising a spec based on review comments to address issues and improve quality scores.
Engineering critic for backlog prioritization debates. Challenges proposed rankings with feasibility concerns, hidden complexity, and realistic effort estimates.
Analyzes code changes for quality issues, code smells, SOLID violations, LLM-generated code problems, and refactoring opportunities. Reports findings with severity, evidence, and suggested fixes.
Design fix plans based on root cause analysis. Use after root cause is identified to plan specific code changes and test cases needed to fix the bug.
Split complex issues into smaller, implementable sub-issues. Called automatically when ComplexityGate determines an issue needs splitting.
Review and score engineering specs against a quality rubric. Use when evaluating a spec draft before implementation to ensure it meets quality standards and identifies potential issues.
Review and score engineering specs against a startup-focused quality rubric. Penalize over-engineering and reward simplicity.
Champion prioritization of discovered opportunities. Advocates for the most impactful, actionable items based on team velocity, business value, and technical feasibility.
Chief Architect review - critically evaluate peer feedback on an engineering spec. Integrate valid suggestions, push back on scope creep, and maintain alignment with the PRD. Enforce startup simplicity.
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
Synthesizes analyst findings with critic feedback. Produces final recommendations and generates TDD-compatible refactor plans for approved issues.
Find and safely claim the next Beads task with conflict checking. Use when looking for work, when finishing a task and need the next one, when the user mentions "next task" or "what should I work on", or when c...
Decompose a phase plan into atomic beads and sub-beads. Use when breaking down a phase into tasks, when the user mentions "decompose" or "break down", when creating beads from a plan, or when structuring work f...
New agent startup checklist for Agent Mail and Beads. Use when starting a new agent session, when the user says "prime" or "startup", or when beginning work on a multi-agent project.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.