[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D4QT5KBSG96SY9ASNWFN0P":3,"skill-same:01M6D4QT5KBSG96SY9ASNWFN0P":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6D4QT5KBSG96SY9ASNWFN0P","burn-rate",null,"Estimate monthly burn rate from infrastructure signals and calculate payback period against revenue projections","GeorgeQLe\u002Fagentic-skills","GeorgeQLe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21134126?v=4","01M6D2JP418S0VGJGF8M93EC3H","George Le","01M6D2JPBAKYD82TA5FS6HKQ3D",1,"MIT","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-ops\u002Fclaude\u002Fburn-rate\u002Farchive\u002Fv0.2\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"burn rate","infrastructure","analysis","team","calculate","v0","runway","only","focus","signals","2026-11-10 10:12:30",false,"---\nname: burn-rate\ndescription: Estimate monthly burn rate from infrastructure signals and calculate payback period against revenue projections\ntype: analysis\nversion: v0.2\nargument-hint: \"[optional: focus area e.g. \\\"infrastructure only\\\", \\\"team costs\\\", \\\"runway\\\"]\"\n---\n\n# Burn Rate — Infrastructure-Grounded Cost & Runway Analysis\n\nAnalyzes a project's infrastructure, third-party services, and team costs to estimate monthly burn rate, then calculates payback period and break-even against revenue projections. Bridges the gap between `\u002Fmonetization` (abstract unit economics) and `\u002Fscale-audit` (infrastructure readiness) with concrete, dollar-denominated cost projections.\n\n## Prerequisites\n\n- **Hard**: None — can run on any codebase.\n- **Soft**: Read these if they exist — each adds revenue\u002Fcost context:\n  - `research\u002Fmonetization.md` (or `research\u002F{app}\u002Fmonetization.md`) — pricing tiers, unit economics, revenue model\n  - `research\u002Fmetrics.md` (or `research\u002F{app}\u002Fmetrics.md`) — business metrics, customer counts\n  - `research\u002Fgtm.md` (or `research\u002F{app}\u002Fgtm.md`) — revenue projections, channel costs\n  - `research\u002Ficp.md` (or `research\u002F{app}\u002Ficp.md`) — market context, buyer budget\n  - `CLAUDE.md`, `README` — product context\n\n## Process\n\n### 0. App Scope Resolution (Monorepo Support)\n\nBefore starting, determine the app scope:\n\n1. If `$ARGUMENTS` specifies an app name matching a subdirectory of `research\u002F`, use it.\n2. If `research\u002F` contains subdirectories (excluding files), list them and ask the user which app to target. If only one subdirectory exists, use it automatically.\n3. If no subdirectories exist, proceed with flat structure (single-product mode).\n\nWhen app scope `{app}` is active:\n- Read\u002Fwrite research from `research\u002F{app}\u002F` instead of `research\u002F`\n- Also read `research\u002Fmonetization.md` (cross-app overview) for broader context\n\n### 1. Load Context\n\na) Read infrastructure files — check for existence of each and read those found:\n   - **Container\u002Forchestration**: `Dockerfile`, `docker-compose.yml`, `docker-compose.*.yml`\n   - **IaC**: `terraform\u002F`, `pulumi\u002F`, `cdk\u002F`, `cloudformation\u002F`\n   - **Kubernetes**: `k8s\u002F`, `kubernetes\u002F`, `*.yaml` in deploy directories, Helm charts\n   - **CI\u002FCD**: `.github\u002Fworkflows\u002F`, `.circleci\u002F`, `.gitlab-ci.yml`, `Jenkinsfile`\n   - **Serverless**: `serverless.yml`, `serverless.ts`, `sam-template.yaml`\n   - **PaaS**: `fly.toml`, `render.yaml`, `vercel.json`, `netlify.toml`, `railway.json`, `Procfile`, `app.yaml`, `heroku.yml`\n   - **Cloud config**: AWS (`samconfig.toml`, `cdk.json`), GCP (`app.yaml`, `.gcloudignore`), Azure (`azure-pipelines.yml`, `host.json`)\n\nb) Read dependency files for third-party service SDKs:\n   - `package.json`, `yarn.lock`, `pnpm-lock.yaml`\n   - `requirements.txt`, `Pipfile`, `pyproject.toml`\n   - `Cargo.toml`, `go.mod`, `Gemfile`, `build.gradle`, `pom.xml`\n   - Look for: Stripe, Twilio, SendGrid, Resend, AWS SDK, GCP SDK, Azure SDK, OpenAI, Anthropic, Auth0, Clerk, Datadog, Sentry, New Relic, Algolia, Typesense, Supabase, PlanetScale, Neon, etc.\n\nc) Read environment templates for service API keys:\n   - `.env.example`, `.env.template`, `.env.sample`, `.env.development`\n   - Look for: API keys, service URLs, database connection strings that imply paid services\n\nd) Read existing research documents (soft prerequisites listed above) — extract:\n   - Revenue projections, pricing tiers, MRR\u002FARR estimates\n   - Unit economics (CAC, LTV, margins)\n   - Customer counts or projections\n   - Business metrics\n\ne) Read `CLAUDE.md` and `README` for product context.\n\n### 2. Infrastructure Cost Detection\n\nScan codebase and build a cost inventory across these categories:\n\n| Category | What to detect |\n|----------|---------------|\n| **Compute** | Cloud provider configs (AWS\u002FGCP\u002FAzure), container orchestration (ECS, k8s, Cloud Run), serverless (Lambda, Cloud Functions), PaaS (Heroku, Fly, Railway, Render, Vercel, Netlify) |\n| **Database** | Database connection strings\u002Fconfigs — Postgres, MySQL, MongoDB, Redis, DynamoDB, Firestore, Supabase, PlanetScale, Neon, CockroachDB |\n| **Storage** | S3\u002FGCS\u002FAzure Blob configs, CDN configs (CloudFront, Cloudflare), file upload services |\n| **Third-party services** | SDK imports and API key references — email (SendGrid, SES, Resend, Postmark), payments (Stripe), auth (Auth0, Clerk, Supabase Auth), monitoring (Datadog, Sentry, New Relic, Grafana Cloud), search (Algolia, Typesense, Meilisearch), AI\u002FML (OpenAI, Anthropic, Replicate, Hugging Face) |\n| **CI\u002FCD** | GitHub Actions minutes, CircleCI, GitLab CI — from workflow configs |\n| **DNS\u002FDomain** | Domain configs if detectable (Cloudflare, Route53) |\n\nFor each detected service:\na) Use WebSearch (at least 4-6 queries) to find current pricing for the detected services. Prioritize the most expensive categories.\nb) Estimate monthly cost using reasonable defaults for a startup-stage project.\nc) Note all assumptions (instance size, tier, usage level).\nd) Assign confidence: **High** (pricing page with clear tiers), **Medium** (usage-dependent, estimated from codebase signals), **Low** (detected but usage unknown).\n\n### 3. Interview — Fill Cost Gaps\n\nUse AskUserQuestion (2-3 focused questions):\n\na) Present detected infrastructure with estimated costs in a table. Ask:\n   - \"Here's what I found in the codebase. Are these estimates roughly right? Any services I missed or got wrong?\"\n\nb) Ask about team and operational costs:\n   - \"What's your team size and approximate fully-loaded cost per person per month? (Or total monthly team cost if easier)\"\n   - \"Any major non-infra costs I can't see in code? (marketing spend, tools\u002Fsubscriptions, office, legal, etc.)\"\n\nc) If revenue data wasn't found in research docs, ask:\n   - \"What's your current or projected monthly revenue? (MRR if live, projected if pre-revenue)\"\n\n### 4. Revenue Projections\n\na) Load revenue data from existing research docs:\n   - `monetization.md` — pricing tiers, revenue model\n   - `gtm.md` — revenue projections, traction targets\n   - `metrics.md` — business metrics, customer counts\n\nb) Present what was found as defaults. Use AskUserQuestion:\n   - \"I found these revenue figures in your research docs: [summary]. Are these current? Please confirm or override with actual numbers.\"\n   - Ask for: current MRR\u002FARR (or projected if pre-revenue), monthly growth rate assumption, customer count (current or projected)\n   - Ask for cash on hand (for runway calculation) — this is optional\n\n### 5. Calculate & Present\n\nCompute the following (with all assumptions visible):\n\na) **Monthly Burn Rate** = infrastructure + team + other costs\n   - Break down by category with percentages\n\nb) **Runway** = cash on hand \u002F monthly burn rate\n   - Only if cash position was provided\n   - Show in months\n\nc) **Payback Period** = total investment to date \u002F monthly net revenue\n   - Net revenue = gross revenue - infrastructure costs\n   - If pre-revenue, note as \"N\u002FA — pre-revenue\"\n\nd) **Break-even Point** = month when cumulative revenue exceeds cumulative costs\n   - Model three scenarios: conservative (50% of base growth), base, optimistic (150% of base growth)\n   - If pre-revenue with no projections, skip\n\ne) **Cost per Customer** = infrastructure costs \u002F customer count\n   - Only if customer count is known or estimable\n\nf) **Cost Optimization Opportunities** — identify quick wins:\n   - Over-provisioned resources\n   - Services with cheaper alternatives\n   - Free tier headroom not being used\n   - Reserved instance \u002F committed use discounts\n\nPresent the full analysis to the user. Use AskUserQuestion:\n- \"Here's the complete burn rate analysis. Ready to write to `research\u002Fburn-rate.md`? Anything to adjust?\"\n\n### 6. Downstream Impact Check\n\nAfter writing, check for downstream research documents that may be affected. Only check documents that exist on disk.\n\n**Downstream documents to check** (use `{app}\u002F` prefix when app scope is active):\n- `research\u002Fmonetization.md`\n\nFor each existing downstream document:\n1. Read it — focus on `> Based on:` header, `## Summary`, and sections that reference cost assumptions, unit economics, or margins\n2. Identify **specific conflicts**: claims, assumptions, or references that contradict the burn rate analysis. Examples:\n   - Gross margin estimates that don't account for actual infrastructure costs\n   - Unit economics assumptions that use different cost figures\n   - Payback period estimates that diverge from the infrastructure-grounded calculation\n3. Note each conflict: downstream file, section, the stale claim (quote it), and what it should now say\n\n**Classify the impact**:\n- **None**: No downstream documents exist, or no conflicts found. Skip display entirely.\n- **Minor** (1-2 small conflicts): Display conflicts to user inline.\n- **Major** (3+ conflicts OR a foundational assumption changed — e.g., burn rate is 2x+ what monetization assumed): Display conflicts and strongly recommend `\u002Freconcile-research`.\n\n### 7. Populate Next Steps\n\nCheck which files exist to populate the `## Next Steps` section contextually. Include 3-5 applicable items with \"Pick one:\" framing:\n\n**Impact-aware adjustments:**\n- IF downstream impact is **Major**: prepend `\u002Freconcile-research — [N] conflicts found in downstream docs` as the first item\n- IF downstream impact is **Minor**: annotate relevant skill suggestions with \"(stale — [brief description])\"\n- If downstream impact has not been classified yet, run the downstream impact check against the proposed output before selecting the final recommendation. Do not emit a Minor\u002FMajor impact recommendation speculatively.\n\nConditional items:\n- IF no `research\u002Fmonetization.md`: check `.agents\u002Fproject.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `\u002Fpack install business-growth` first; if `business-growth` is enabled, recommend `\u002Fmonetization` — Build pricing strategy informed by actual infrastructure costs\n- IF `research\u002Fmonetization.md` exists but unit economics differ: check `.agents\u002Fproject.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `\u002Fpack install business-growth` first; if `business-growth` is enabled, recommend `\u002Fmonetization` — Update unit economics with infrastructure-grounded costs\n- IF no `research\u002Fgtm.md`: check `.agents\u002Fproject.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `\u002Fpack install business-growth` first; if `business-growth` is enabled, recommend `\u002Fgtm` — Build go-to-market plan with cost-aware pricing\n- IF no `research\u002Fmetrics.md`: check `.agents\u002Fproject.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `\u002Fpack install business-growth` first; if `business-growth` is enabled, recommend `\u002Fmetrics` — Define metrics to track burn rate health (cost per customer, infrastructure efficiency)\n- IF no `research\u002Fscale-audit.md` and infrastructure is complex: `\u002Fscale-audit` — Evaluate infrastructure readiness before scaling costs\n- IF codebase exists and optimization opportunities found: check `.agents\u002Fproject.json.enabled_packs` for `product-design` — if `product-design` is not enabled, recommend `\u002Fpack install product-design` first; if `product-design` is enabled, recommend `\u002Fbrainstorm` — Explore cost optimization as a feature priority\n\n### 8. Write Output\n\nOnly after the user has validated the findings, write the output file.\n\n## Output\n\n### `research\u002Fburn-rate.md` (or `research\u002F{app}\u002Fburn-rate.md`)\n\n```markdown\n# Burn Rate Analysis\n\n> Based on: codebase infrastructure analysis[, research\u002Fmonetization.md, research\u002Fmetrics.md, research\u002Fgtm.md]\n> Date: [current date]\n\n## Summary\n[2-3 sentences: total monthly burn rate, largest cost drivers, and runway\u002Fpayback headline]\n\n## Infrastructure Cost Breakdown\n\n| Service | Category | Monthly Estimate | Assumption | Confidence |\n|---------|----------|-----------------|------------|------------|\n| [e.g. AWS EC2] | Compute | $X | [e.g. t3.medium, on-demand] | High\u002FMedium\u002FLow |\n| [e.g. Supabase] | Database | $X | [e.g. Pro plan] | High\u002FMedium\u002FLow |\n| ... | ... | ... | ... | ... |\n| **Infrastructure Total** | | **$X** | | |\n\n## Team & Operational Costs\n\n| Category | Monthly Cost | Notes |\n|----------|-------------|-------|\n| Team (N people) | $X | [fully-loaded cost per person] |\n| Marketing | $X | [if provided] |\n| Tools & Subscriptions | $X | [if provided] |\n| Other | $X | [if provided] |\n| **Operational Total** | | **$X** |\n\n## Total Monthly Burn Rate\n\n| Category | Monthly Cost | % of Total |\n|----------|-------------|-----------|\n| Infrastructure | $X | X% |\n| Team | $X | X% |\n| Other Operational | $X | X% |\n| **Total** | **$X** | **100%** |\n\n## Revenue Projections\n\n| Metric | Value | Source |\n|--------|-------|--------|\n| Current MRR | $X | [user-provided \u002F monetization.md] |\n| Growth Rate | X%\u002Fmo | [assumption] |\n| Customer Count | N | [user-provided \u002F metrics.md] |\n| Projected MRR (6 mo) | $X | [calculated] |\n| Projected MRR (12 mo) | $X | [calculated] |\n\n## Payback Period Analysis\n\n| Scenario | Monthly Growth | Break-even Month | Payback Period |\n|----------|---------------|-----------------|----------------|\n| Conservative | X%\u002Fmo | Month N | N months |\n| Base | X%\u002Fmo | Month N | N months |\n| Optimistic | X%\u002Fmo | Month N | N months |\n\n### Assumptions\n[List key assumptions behind each scenario]\n\n## Runway\n\n| Metric | Value |\n|--------|-------|\n| Cash on Hand | $X |\n| Monthly Burn | $X |\n| Runway | N months |\n| Runway at 50% Burn | N months |\n\n[Omit this section if cash position was not provided]\n\n## Cost per Customer\n\n| Metric | Value |\n|--------|-------|\n| Infrastructure Cost \u002F Customer | $X |\n| Total Cost \u002F Customer | $X |\n| Revenue \u002F Customer (ARPU) | $X |\n| Gross Margin per Customer | X% |\n\n[Omit this section if customer count is unknown]\n\n## Cost Optimization Opportunities\n\n1. **[Opportunity]** — [description, estimated savings]\n2. **[Opportunity]** — [description, estimated savings]\n3. ...\n\n## Assumptions & Data Gaps\n[List all assumptions made, data that would improve accuracy, and recommended next steps for better estimates]\n\n\u003C!-- Only include this section when downstream impact is Minor or Major. Omit entirely for None. -->\n## Downstream Impact\n\n> Checked: [list of downstream docs checked]\n> Impact: Minor | Major\n\n### Conflicts Found\n\n1. **research\u002F[file].md** — [Section Name]\n   - **Stale**: \"[exact quote from downstream doc]\"\n   - **Now**: [what this skill's output says instead]\n\n[For Major only:]\n> **Recommended action**: Run `\u002Freconcile-research` to audit and fix all affected downstream documents.\n\n## Next Steps\n\nPick one:\n- [conditional items from step 7 — only include items whose conditions are met]\n```\n\n### `research\u002Fburn-rate-interview.md` (or `research\u002F{app}\u002Fburn-rate-interview.md`)\nRaw interview log — questions asked, infrastructure detected, user responses, cost validations, and a closing summary of key figures and assumptions.\n\nCreate the `research\u002F` (or `research\u002F{app}\u002F`) directory if it doesn't exist.\n\n## Task Classification\n\nWhen this skill produces follow-up work, file it by execution semantics:\n\n- Immediately actionable implementation or documentation work goes in `tasks\u002Ftodo.md`.\n- Human-only external actions tied to automated steps go in `tasks\u002Fmanual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`; repo edits, SDK wiring, generated assets, local commands, tests, audits, and authenticated CLI\u002FAPI work stay in `tasks\u002Ftodo.md`.\n- One-time condition-gated records, baselines, or future measurements go in `tasks\u002Frecord-todo.md` with source, condition, non-blocking reason, evidence, and promotion rule.\n- Cadence-based reviews, playtests, adoption checks, investor updates, retros, or docs-health checks go in `tasks\u002Frecurring-todo.md` with cadence, owner\u002Fagent, next due, evidence path, and escalation conditions.\n- Do not put non-blocking records or recurring obligations in `tasks\u002Ftodo.md` unless they have been explicitly promoted into current execution work.\n\n## Constraints\n\n- **Evidence-based costs.** Every cost estimate must trace to a detected service in the codebase or a user-provided figure. Do not invent costs.\n- **Present before writing.** Never write output files until the full analysis has been presented and validated by the user.\n- **State assumptions.** Every cost estimate must include the assumption behind it (tier, instance size, usage level) and a confidence level. Never present estimates as facts.\n- **Don't prescribe architecture changes.** If infrastructure is over-provisioned or poorly structured, note it as a cost optimization opportunity — architecture decisions belong in `\u002Fscale-audit` or `\u002Fbrainstorm`.\n- **Don't duplicate monetization.** If `research\u002Fmonetization.md` already has unit economics, compare and reconcile rather than contradict. Note any differences and ask the user to resolve.\n- **Do not overwrite existing `research\u002Fburn-rate.md`** (or `research\u002F{app}\u002Fburn-rate.md`) without asking the user first.\n- **Minimum research depth**: at least 4 WebSearch queries for pricing data before presenting cost estimates.\n- **Use current pricing.** Always search for current pricing — cached or memorized pricing may be outdated.\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fburn-rate-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","# Burn Rate — Infrastructure-Grounded Cost & Runway Analysis\n\nAnalyzes a project's infrastructure, third-party services, and team costs to estimate monthly burn rate, then calculates payback period and break-even against revenue projections. Bridges the gap between `\u002Fmonetization` (abstract unit economics) and `\u002Fscale-audit` (infrastructure readiness) with concrete, dollar-denominated cost projections.\n\n## Prerequisites\n\n- **Hard**: None — can run on any codebase.\n- **Soft**: Read these if they exist — each adds revenue\u002Fcost context:\n  - `research\u002Fmonetization.md` (or `research\u002F{app}\u002Fmonetization.md`) — pricing tiers, unit economics, revenue model\n  - `research\u002Fmetrics.md` (or `research\u002F{app}\u002Fmetrics.md`) — business metrics, customer counts\n  - `research\u002Fgtm.md` (or `research\u002F{app}\u002Fgtm.md`) — revenue projections, channel costs\n  - `research\u002Ficp.md` (or `research\u002F{app}\u002Ficp.md`) — market context, buyer budget\n  - `CLAUDE.md`, `README` — product context\n\n## Process\n\n### 0. App Scope Resolution (Monorepo Support)\n\nBefore starting, determine the app scope:\n\n1. If `$ARGUMENTS` specifies an app name matching a subdirectory of `research\u002F`, use it.\n2. If `research\u002F` contains subdirectories (excluding files), list them and ask the user which app to target. If only one subdirectory exists, use it automatically.\n3. If no subdirectories exist, proceed with flat structure (single-product mode).\n\nWhen app scope `{app}` is active:\n- Read\u002Fwrite research from `research\u002F{app}\u002F` instead of `research\u002F`\n- Also read `research\u002Fmonetization.md` (cross-app overview) for broader context\n\n### 1. Load Context\n\na) Read infrastructure files — check for existence of each and read those found:\n   - **Container\u002Forchestration**: `Dockerfile`, `docker-compose.yml`, `docker-compose.*.yml`\n   - **IaC**: `terraform\u002F`, `pulumi\u002F`, `cdk\u002F`, `cloudformation\u002F`\n   - **Kubernetes**: `k8s\u002F`, `kubernetes\u002F`, `*.yaml` in deploy directories, Helm charts\n   - **CI\u002FCD**: `.github\u002Fworkflows\u002F`, `.circleci\u002F`, `.gitlab-ci.yml`, `Jenkinsfile`\n   - **Serverless**: `serverless.yml`, `serverless.ts`, `sam-template.yaml`\n   - **PaaS**: `fly.toml`, `render.yaml`, `vercel.json`, `netlify.toml`, `railway.json`, `Procfile`, `app.yaml`, `heroku.yml`\n   - **Cloud config**: AWS (`samconfig.toml`, `cdk.json`), GCP (`app.yaml`, `.gcloudignore`), Azure (`azure-pipelines.yml`, `host.json`)\n\nb) Read dependency files for third-party service SDKs:\n   - `package.json`, `yarn.lock`, `pnpm-lock.yaml`\n   - `requirements.txt`, `Pipfile`, `pyproject.toml`\n   - `Cargo.toml`, `go.mod`, `Gemfile`, `build.gradle`, `pom.xml`\n   - Look for: Stripe, Twilio, SendGrid, Resend, AWS SDK, GCP SDK, Azure SDK, OpenAI, Anthropic, Auth0, Clerk, Datadog, Sentry, New Relic, Algolia, Typesense, Supabase, PlanetScale, Neon, etc.\n\nc) Read environment templates for service API keys:\n   - `.env.example`, `.env.template`, `.env.sample`, `.env.development`\n   - Look for: API keys, service URLs, database connection strings that imply paid services\n\nd) Read existing research documents (soft prerequisites listed above) — extract:\n   - Revenue projections, pricing tiers, MRR\u002FARR estimates\n   - Unit economics (CAC, LTV, margins)\n   - Customer counts or projections\n   - Business metrics\n\ne) Read `CLAUDE.md` and `README` for product context.\n\n### 2. Infrastructure Cost Detection\n\nScan codebase and build a cost inventory across these categories:\n\n| Category | What to detect |\n|----------|---------------|\n| **Compute** | Cloud provider configs (AWS\u002FGCP\u002FAzure), container orchestration (ECS, k8s, Cloud Run), serverless (Lambda, Cloud Functions), PaaS (Heroku, Fly, Railway, Render, Vercel, Netlify) |\n| **Database** | Database connection strings\u002Fconfigs — Postgres, MySQL, MongoDB, Redis, DynamoDB, Firestore, Supabase, PlanetScale, Neon, CockroachDB |\n| **Storage** | S3\u002FGCS\u002FAzure Blob configs, CDN configs (CloudFront, Cloudflare), file upload services |\n| **Third-party services** | SDK imports and API key references — email (SendGrid, SES, Resend, Postmark), payments (Stripe), auth (Auth0, Clerk, Supabase Auth), monitoring (Datadog, Sentry, New Relic, Grafana Cloud), search (Algolia, Typesense, Meilisearch), AI\u002FML (OpenAI, Anthropic, Replicate, Hugging Face) |\n| **CI\u002FCD** | GitHub Actions minutes, CircleCI, GitLab CI — from workflow configs |\n| **DNS\u002FDomain** | Domain configs if detectable (Cloudflare, Route53) |\n\nFor each detected service:\na) Use WebSearch (at least 4-6 queries) to find current pricing for the detected services. Prioritize the most expensive categories.\nb) Estimate monthly cost using reasonable defaults for a startup-stage project.\nc) Note all assumptions (instance size, tier, usage level).\nd) Assign confidence: **High** (pricing page with clear tiers), **Medium** (usage-dependent, estimated from codebase signals), **Low** (detected but usage unknown).\n\n### 3. Interview — Fill Cost Gaps\n\nUse AskUserQuestion (2-3 focused questions):\n\na) Present detected infrastructure with estimated costs in a table. Ask:\n   - \"Here's what I found in the codebase. Are these estimates roughly right? Any services I missed or got wrong?\"\n\nb) Ask about team and operational costs:\n   - \"What's your team size and approximate fully-loaded cost per person per month? (Or total monthly team cost if easier)\"\n   - \"Any major non-infra costs I can't see in code? (marketing spend, tools\u002Fsubscriptions, office, legal, etc.)\"\n\nc) If revenue data wasn't found in research docs, ask:\n   - \"What's your current or projected monthly revenue? (MRR if live, projected if pre-revenue)\"\n\n### 4. Revenue Projections\n\na) Load revenue data from existing research docs:\n   - `monetization.md` — pricing tiers, revenue model\n   - `gtm.md` — revenue projections, traction targets\n   - `metrics.md` — business metrics, customer counts\n\nb) Present what was found as defaults. Use AskUserQuestion:\n   - \"I found these revenue figures in your research docs: [summary]. Are these current? Please confirm or override with actual numbers.\"\n   - Ask for: current MRR\u002FARR (or projected if pre-revenue), monthly growth rate assumption, customer count (current or projected)\n   - Ask for cash on hand (for runway calculation) — this is optional\n\n### 5. Calculate & Present\n\nCompute the following (with all assumptions visible):\n\na) **Monthly Burn Rate** = infrastructure + team + other costs\n   - Break down by category with percentages\n\nb) **Runway** = cash on hand \u002F monthly burn rate\n   - Only if cash position was provided\n   - Show in months\n\nc) **Payback Period** = total investment to date \u002F monthly net revenue\n   - Net revenue = gross revenue - infrastructure costs\n   - If pre-revenue, note as \"N\u002FA — pre-revenue\"\n\nd) **Break-even Point** = month when cumulative revenue exceeds cumulative costs\n   - Model three scenarios: conservative (50% of base growth), base, optimistic (150% of base growth)\n   - If pre-revenue with no projections, skip\n\ne) **Cost per Customer** = infrastructure costs \u002F customer count\n   - Only if customer count is known or estimable\n\nf) **Cost Optimization Opportunities** — identify quick wins:\n   - Over-provisioned resources\n   - Services with cheaper alternatives\n   - Free tier headroom not being used\n   - Reserved instance \u002F committed use discounts\n\nPresent the full analysis to the user. Use AskUserQuestion:\n- \"Here's the complete burn rate analysis. Ready to write to `research\u002Fburn-rate.md`? Anything to adjust?\"\n\n### 6. Downstream Impact Check\n\nAfter writing, check for downstream research documents that may be affected. Only check documents that exist on disk.\n\n**Downstream documents to check** (use `{app}\u002F` prefix when app scope is active):\n- `research\u002Fmonetization.md`\n\nFor each existing downstream document:\n1. Read it — focus on `> Based on:` header, `## Summary`, and sections that reference cost assumptions, unit economics, or margins\n2. Identify **specific conflicts**: claims, assumptions, or references that contradict the burn rate analysis. Examples:\n   - Gross margin estimates that don't account for actual infrastructure costs\n   - Unit economics assumptions that use different cost figures\n   - Payback period estimates that diverge from the infrastructure-grounded calculation\n3. Note each conflict: downstream file, section, the stale claim (quote it), and what it should now say\n\n**Classify the impact**:\n- **None**: No downstream documents exist, or no conflicts found. Skip display entirely.\n- **Minor** (1-2 small conflicts): Display conflicts to user inline.\n- **Major** (3+ conflicts OR a foundational assumption changed — e.g., burn rate is 2x+ what monetization assumed): Display conflicts and strongly recommend `\u002Freconcile-research`.\n\n### 7. Populate Next Steps\n\nCheck which files exist to populate the `## Next Steps` section contextually. Include 3-5 applicable items with \"Pick one:\" framing:\n\n**Impact-aware adjustments:**\n- IF downstream impact is **Major**: prepend `\u002Freconcile-research — [N] conflicts found in downstream docs` as the first item\n- IF downstream impact is **Minor**: annotate relevant skill suggestions with \"(stale — [brief description])\"\n- If downstream impact has not been classified yet, run the downstream impact check against the proposed output before selecting the final recommendation. Do not emit a Minor\u002FMajor impact recommendation speculatively.\n\nConditional items:\n- IF no `research\u002Fmonetization.md`: check `.agents\u002Fproject.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `\u002Fpack install business-growth` first; if `business-growth` is enabled, recommend `\u002Fmonetization` — Build pricing strategy informed by actual infrastructure costs\n- IF `research\u002Fmonetization.md` exists but unit economics differ: check `.agents\u002Fproject.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `\u002Fpack install business-growth` first; if `business-growth` is enabled, recommend `\u002Fmonetization` — Update unit economics with infrastructure-grounded costs\n- IF no `research\u002Fgtm.md`: check `.agents\u002Fproject.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `\u002Fpack install business-growth` first; if `business-growth` is enabled, recommend `\u002Fgtm` — Build go-to-market plan with cost-aware pricing\n- IF no `research\u002Fmetrics.md`: check `.agents\u002Fproject.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `\u002Fpack install business-growth` first; if `business-growth` is enabled, recommend `\u002Fmetrics` — Define metrics to track burn rate health (cost per customer, infrastructure efficiency)\n- IF no `research\u002Fscale-audit.md` and infrastructure is complex: `\u002Fscale-audit` — Evaluate infrastructure readiness before scaling costs\n- IF codebase exists and optimization opportunities found: check `.agents\u002Fproject.json.enabled_packs` for `product-design` — if `product-design` is not enabled, recommend `\u002Fpack install product-design` first; if `product-design` is enabled, recommend `\u002Fbrainstorm` — Explore cost optimization as a feature priority\n\n### 8. Write Output\n\nOnly after the user has validated the findings, write the output file.\n\n## Output\n\n### `research\u002Fburn-rate.md` (or `research\u002F{app}\u002Fburn-rate.md`)\n\n```markdown\n# Burn Rate Analysis\n\n> Based on: codebase infrastructure analysis[, research\u002Fmonetization.md, research\u002Fmetrics.md, research\u002Fgtm.md]\n> Date: [current date]\n\n## Summary\n[2-3 sentences: total monthly burn rate, largest cost drivers, and runway\u002Fpayback headline]\n\n## Infrastructure Cost Breakdown\n\n| Service | Category | Monthly Estimate | Assumption | Confidence |\n|---------|----------|-----------------|------------|------------|\n| [e.g. AWS EC2] | Compute | $X | [e.g. t3.medium, on-demand] | High\u002FMedium\u002FLow |\n| [e.g. Supabase] | Database | $X | [e.g. Pro plan] | High\u002FMedium\u002FLow |\n| ... | ... | ... | ... | ... |\n| **Infrastructure Total** | | **$X** | | |\n\n## Team & Operational Costs\n\n| Category | Monthly Cost | Notes |\n|----------|-------------|-------|\n| Team (N people) | $X | [fully-loaded cost per person] |\n| Marketing | $X | [if provided] |\n| Tools & Subscriptions | $X | [if provided] |\n| Other | $X | [if provided] |\n| **Operational Total** | | **$X** |\n\n## Total Monthly Burn Rate\n\n| Category | Monthly Cost | % of Total |\n|----------|-------------|-----------|\n| Infrastructure | $X | X% |\n| Team | $X | X% |\n| Other Operational | $X | X% |\n| **Total** | **$X** | **100%** |\n\n## Revenue Projections\n\n| Metric | Value | Source |\n|--------|-------|--------|\n| Current MRR | $X | [user-provided \u002F monetization.md] |\n| Growth Rate | X%\u002Fmo | [assumption] |\n| Customer Count | N | [user-provided \u002F metrics.md] |\n| Projected MRR (6 mo) | $X | [calculated] |\n| Projected MRR (12 mo) | $X | [calculated] |\n\n## Payback Period Analysis\n\n| Scenario | Monthly Growth | Break-even Month | Payback Period |\n|----------|---------------|-----------------|----------------|\n| Conservative | X%\u002Fmo | Month N | N months |\n| Base | X%\u002Fmo | Month N | N months |\n| Optimistic | X%\u002Fmo | Month N | N months |\n\n### Assumptions\n[List key assumptions behind each scenario]\n\n## Runway\n\n| Metric | Value |\n|--------|-------|\n| Cash on Hand | $X |\n| Monthly Burn | $X |\n| Runway | N months |\n| Runway at 50% Burn | N months |\n\n[Omit this section if cash position was not provided]\n\n## Cost per Customer\n\n| Metric | Value |\n|--------|-------|\n| Infrastructure Cost \u002F Customer | $X |\n| Total Cost \u002F Customer | $X |\n| Revenue \u002F Customer (ARPU) | $X |\n| Gross Margin per Customer | X% |\n\n[Omit this section if customer count is unknown]\n\n## Cost Optimization Opportunities\n\n1. **[Opportunity]** — [description, estimated savings]\n2. **[Opportunity]** — [description, estimated savings]\n3. ...\n\n## Assumptions & Data Gaps\n[List all assumptions made, data that would improve accuracy, and recommended next steps for better estimates]\n\n\u003C!-- Only include this section when downstream impact is Minor or Major. Omit entirely for None. -->\n## Downstream Impact\n\n> Checked: [list of downstream docs checked]\n> Impact: Minor | Major\n\n### Conflicts Found\n\n1. **research\u002F[file].md** — [Section Name]\n   - **Stale**: \"[exact quote from downstream doc]\"\n   - **Now**: [what this skill's output says instead]\n\n[For Major only:]\n> **Recommended action**: Run `\u002Freconcile-research` to audit and fix all affected downstream documents.\n\n## Next Steps\n\nPick one:\n- [conditional items from step 7 — only include items whose conditions are met]\n```\n\n### `research\u002Fburn-rate-interview.md` (or `research\u002F{app}\u002Fburn-rate-interview.md`)\nRaw interview log — questions asked, infrastructure detected, user responses, cost validations, and a closing summary of key figures and assumptions.\n\nCreate the `research\u002F` (or `research\u002F{app}\u002F`) directory if it doesn't exist.\n\n## Task Classification\n\nWhen this skill produces follow-up work, file it by execution semantics:\n\n- Immediately actionable implementation or documentation work goes in `tasks\u002Ftodo.md`.\n- Human-only external actions tied to automated steps go in `tasks\u002Fmanual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`; repo edits, SDK wiring, generated assets, local commands, tests, audits, and authenticated CLI\u002FAPI work stay in `tasks\u002Ftodo.md`.\n- One-time condition-gated records, baselines, or future measurements go in `tasks\u002Frecord-todo.md` with source, condition, non-blocking reason, evidence, and promotion rule.\n- Cadence-based reviews, playtests, adoption checks, investor updates, retros, or docs-health checks go in `tasks\u002Frecurring-todo.md` with cadence, owner\u002Fagent, next due, evidence path, and escalation conditions.\n- Do not put non-blocking records or recurring obligations in `tasks\u002Ftodo.md` unless they have been explicitly promoted into current execution work.\n\n## Constraints\n\n- **Evidence-based costs.** Every cost estimate must trace to a detected service in the codebase or a user-provided figure. Do not invent costs.\n- **Present before writing.** Never write output files until the full analysis has been presented and validated by the user.\n- **State assumptions.** Every cost estimate must include the assumption behind it (tier, instance size, usage level) and a confidence level. Never present estimates as facts.\n- **Don't prescribe architecture changes.** If infrastructure is over-provisioned or poorly structured, note it as a cost optimization opportunity — architecture decisions belong in `\u002Fscale-audit` or `\u002Fbrainstorm`.\n- **Don't duplicate monetization.** If `research\u002Fmonetization.md` already has unit economics, compare and reconcile rather than contradict. Note any differences and ask the user to resolve.\n- **Do not overwrite existing `research\u002Fburn-rate.md`** (or `research\u002F{app}\u002Fburn-rate.md`) without asking the user first.\n- **Minimum research depth**: at least 4 WebSearch queries for pricing data before presenting cost estimates.\n- **Use current pricing.** Always search for current pricing — cached or memorized pricing may be outdated.\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment\u002Fburn-rate-{topic}.html`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":21,"version":34,"description":7,"argument-hint":35},"v0.2","[optional: focus area e.g. \"infrastructure only\", \"team costs\", \"runway\"]","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fbusiness-ops\u002Fclaude\u002Fburn-rate\u002Farchive\u002Fv0.2",0,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills","https:\u002F\u002Fagentic-skills-blush.vercel.app","https:\u002F\u002Fgithub.com\u002FGeorgeQLe","georgeqle.com","George Le is a futurist and serial tech entrepreneur who wants to work toward a world where humanity is free from robotic tasks.","2026-11-10 04:07:24",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill burn-rate",{"tool":52,"command":53},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill burn-rate",{"tool":55,"command":56},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill burn-rate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-ops\u002Fclaude\u002Fburn-rate\u002Farchive\u002Fv0.2\u002FSKILL.md",true,[],[61,72,82,94,109,120],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":29},"01M6G0NJES15RJKZE6YZ0TSYGF","source-checkout-allowed","Valid source-checkout-only fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fsource-checkout-allowed\u002FSKILL.md",[],[68,69,70,26,24,71],"source checkout allowed","checkout","fixture","valid",{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":29},"01M6G0NFZ3R1MNB1E3DVTM0WB7","deck-install-valid","Valid deck install fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fdeck-install\u002FSKILL.md",[],[79,80,81,71,70,24],"deck install valid","deck","install",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":29},"01M6G0ND3QZQC4MDZ9NVB97PT2","codex-pack-guard-valid","Valid Codex Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-pack-guard\u002FSKILL.md",[],[89,90,91,71,92,93,70,24],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"publishedAt":29},"01M6G0NA9YB3NKGZKD3S96JMNB","codex-missing-skill-valid","Valid Codex missing skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-missing-skill-fallback\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[106,107,71,92,24,108,70],"codex missing skill valid","missing","fallback",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":116,"publishedAt":29},"01M6G0N7PC0EKFD40ZWQAXSAQ9","codex-base-skill-fallback-valid","Valid Codex base skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-base-skill-fallback\u002FSKILL.md",[115],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},[71,92,108,117,118,119,24,70],"base skill","codex base skill fallback valid","base",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":29},"01M6G0N4VRR2YKZQ6N3Y6S2BQA","claude-pack-guard-valid","Valid Claude Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fclaude-pack-guard\u002FSKILL.md",[],[71,91,90,127,93,24,70],"claude pack guard valid"]