# Paid Mini-Sprints

Small paid help for teams using AI coding agents in real operations work.

## Best Fit

- Production bug triage from sanitized logs or public repo context
- AI-generated TypeScript, Next.js, Python, or SQL code cleanup
- Code review focused on bugs, regressions, missing tests, and unsafe assumptions
- Deploy smoke checklists and release handoff notes
- Internal workflow automation around GitHub, docs, prompts, or APIs

## Starter Offers

| Offer | Output | Suggested budget |
|---|---|---:|
| Bug triage note | Cause hypothesis, evidence path, next fix step | 30-75 USD equivalent |
| PR risk review | Findings ordered by severity with file/line references | 30-150 USD equivalent |
| Deploy smoke pack | Checklist plus commands/endpoints to verify | 50-150 USD equivalent |
| Small automation spec | Scoped plan and implementation-ready acceptance criteria | 75-200 USD equivalent |
| AI-code cleanup sprint | Small patch or clear handoff after review | Quote after context |

Short buyer menu:

https://github.com/mysubb01/agent-ops-command-pack-teaser/blob/main/SERVICE_MENU.md

## Fixed Starter Requests

- Bug triage note: https://github.com/mysubb01/agent-ops-command-pack-teaser/issues/new?template=starter-bug-triage.yml
- PR risk review: https://github.com/mysubb01/agent-ops-command-pack-teaser/issues/new?template=starter-pr-risk-review.yml
- Deploy smoke pack: https://github.com/mysubb01/agent-ops-command-pack-teaser/issues/new?template=starter-deploy-smoke.yml

## Sample Deliverables

- Bug triage sample: https://mysubb01.github.io/agent-ops-command-pack-teaser/pages/sample-bug-triage-deliverable.html
- PR risk review sample: https://mysubb01.github.io/agent-ops-command-pack-teaser/pages/sample-pr-risk-review-deliverable.html

## Request Work

Open a paid mini-sprint request:

https://github.com/mysubb01/agent-ops-command-pack-teaser/issues/new?template=paid-sprint.yml

External share page:

https://gist.github.com/mysubb01/abfd2f8da7505a24f5cefe377563fb5f

Do not post secrets, tokens, private customer data, payment details, or credentials in a public issue.

## Payment Handoff

- GitHub issues are only for sanitized intake, scope, budget, and acceptance criteria.
- Do not post card, bank, wallet, customer, token, or credential details in public.
- After the scope and quote are accepted, payment link, invoice, or private handoff happens outside the public issue.
- Work starts after scope, delivery format, and payment path are agreed.

## How Scope Is Confirmed

1. You open a public request with sanitized context.
2. I reply with a proposed scope, price, and acceptance criteria.
3. If the scope fits, I provide a private invoice or payment handoff before work starts.
4. Private repo access, sensitive logs, and payment details are handled outside the public issue.
5. Work starts only after scope, delivery format, and payment path are agreed.