capacity-plan
# capacity-plan This Claude Code skill analyzes team capacity, workload allocation, and resource utilization to support quarterly planning and hiring decisions. Use it when assessing whether your team can handle upcoming projects, determining if headcount increases are necessary, evaluating skill gaps, or identifying overallocation issues. Input team size, current work, planned initiatives, and constraints to receive utilization analysis, bottleneck identification, and scenario planning that accounts for realistic capacity targets by role and common planning pitfalls.
git clone --depth 1 https://github.com/openyak/openyak /tmp/capacity-plan && cp -r /tmp/capacity-plan/backend/app/data/plugins/operations/skills/capacity-plan ~/.claude/skills/capacity-planSKILL.md
# /capacity-plan > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Analyze team capacity and plan resource allocation. ## Usage ``` /capacity-plan $ARGUMENTS ``` ## What I Need From You - **Team size and roles**: Who do you have? - **Current workload**: What are they working on? (Upload from project tracker or describe) - **Upcoming work**: What's coming next quarter? - **Constraints**: Budget, hiring timeline, skill requirements ## Planning Dimensions ### People - Available headcount and skills - Current allocation and utilization - Planned hires and timeline - Contractor and vendor capacity ### Budget - Operating budget by category - Project-specific budgets - Variance tracking - Forecast vs. actual ### Time - Project timelines and dependencies - Critical path analysis - Buffer and contingency planning - Deadline management ## Utilization Targets | Role Type | Target Utilization | Notes | |-----------|-------------------|-------| | IC / Specialist | 75-80% | Leave room for reactive work and growth | | Manager | 60-70% | Management overhead, meetings, 1:1s | | On-call / Support | 50-60% | Interrupt-driven work is unpredictable | ## Common Pitfalls - Planning to 100% utilization (no buffer for surprises) - Ignoring meeting load and context-switching costs - Not accounting for vacation, holidays, and sick time - Treating all hours as equal (creative work ≠ admin work) ## Output ```markdown ## Capacity Plan: [Team/Project] **Period:** [Date range] | **Team Size:** [X] ### Current Utilization | Person/Role | Capacity | Allocated | Available | Utilization | |-------------|----------|-----------|-----------|-------------| | [Name/Role] | [hrs/wk] | [hrs/wk] | [hrs/wk] | [X]% | ### Capacity Summary - **Total capacity**: [X] hours/week - **Currently allocated**: [X] hours/week ([X]%) - **Available**: [X] hours/week ([X]%) - **Overallocated**: [X people above 100%] ### Upcoming Demand | Project/Initiative | Start | End | Resources Needed | Gap | |--------------------|-------|-----|-----------------|-----| | [Project] | [Date] | [Date] | [X FTEs] | [Covered/Gap] | ### Bottlenecks - [Skill or role that's oversubscribed] - [Time period with a crunch] ### Recommendations 1. [Hire / Contract / Reprioritize / Delay] 2. [Specific action] ### Scenarios | Scenario | Outcome | |----------|---------| | Do nothing | [What happens] | | Hire [X] | [What changes] | | Deprioritize [Y] | [What frees up] | ``` ## If Connectors Available If **~~project tracker** is connected: - Pull current workload and ticket assignments automatically - Show upcoming sprint or quarter commitments per person If **~~calendar** is connected: - Factor in PTO, holidays, and recurring meeting load - Calculate actual available hours per person ## Tips 1. **Include all work** — BAU, projects, support, meetings. People aren't 100% available for project work. 2. **Plan for buffer** — Target 80% utilization. 100% means no room for surprises. 3. **Update regularly** — Capacity plans go stale fast. Review monthly.
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full ASM JSON, flattened CSV for easy import, and exportable Python code for data engineers. Common triggers include converting instrument files, standardizing lab data, preparing data for upload to LIMS/ELN systems, or generating parser code for production pipelines.
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data. Use when analyzing RNA-seq, WGS/WES, or ATAC-seq data—either local FASTQs or public datasets from GEO/SRA. Triggers on nf-core, Nextflow, FASTQ analysis, variant calling, gene expression, differential expression, GEO reanalysis, GSE/GSM/SRR accessions, or samplesheet creation.
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI, (2) ATAC-seq analysis with PeakVI, (3) CITE-seq multi-modal analysis with totalVI, (4) multiome RNA+ATAC analysis with MultiVI, (5) spatial transcriptomics deconvolution with DestVI, (6) label transfer and reference mapping with scANVI/scArches, (7) RNA velocity with veloVI, or (8) any deep learning-based single-cell method. Triggers include mentions of scVI, scANVI, totalVI, PeakVI, MultiVI, DestVI, veloVI, sysVI, scArches, variational autoencoder, VAE, batch correction, data integration, multi-modal, CITE-seq, multiome, reference mapping, latent space.
Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive visualizations. Use when users request QC analysis, filtering low-quality cells, assessing data quality, or following scverse/scanpy best practices for single-cell analysis.
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
>
>