request-dev

Request work from the developer

This vault runs a two-tier model: the owner runs the business with Claude day-to-day; a developer builds the engineering. Use this skill to hand a need to that developer as a GitHub issue on the firm's repo — the owner never touches GitHub.

Use this when the request needs a new script/skill, a Cloudflare worker, an external API integration, secrets/deploy infrastructure, a schema/type redesign, or a data migration — anything you shouldn't ship as a fragile production hack. For everyday in-vault work (notes, clients, projects, time, invoices), just do it.

Steps

1. Understand the need. Ask the owner only what's necessary: what they want to happen, the business goal, and how urgent. Infer everything else from the vault — don't interrogate them.
2. Classify the type: script | skill | cloudflare-worker | integration | report | schema | other.
3. Gather context from the vault: which clients/projects/notes are involved, any example data, and what "done" looks like (acceptance criteria).
4. File a GitHub issue on the firm's repo (current repo's origin):

   gh label create dev-request --color 5319e7 \
     --description "Work for the firm's developer" 2>/dev/null || true
   gh issue create --label dev-request --title "<short imperative title>" --body "$(cat <<'EOF'
   **What the owner needs**
   <plain-language description>
   
   **Why / business goal**
   <the outcome they want>
   
   **Type:** <script|skill|cloudflare-worker|integration|report|schema|other>
   
   **Vault context**
   - Clients/projects: <wikilinks or note paths>
   - Relevant files: <paths>
   - Example data: <if any>
   
   **Acceptance criteria**
   - [ ] <observable outcome>
   - [ ] <...>
   
   **Notes for the developer**
   <constraints + what you already learned. Reminders: secrets live in Doppler
   (never files); owner-runnable scripts should be stdlib-only Python; workers are
   TypeScript deployed via `doppler run -- npx wrangler deploy`; reusable-across-
   firms work belongs in the marketplace, firm-specific work in this repo. See
   DEVELOPER.md.>
   EOF
   )"
   

5. Tell the owner in plain words: "I've logged this for your developer as issue #: . They'll build it and it'll appear in your vault automatically when it's ready — nothing more for you to do." Include the issue URL.

If GitHub isn't reachable

Don't fail silently. If gh isn't signed in or there's no GitHub remote, write the same request to requests/<YYYY-MM-DD>-<slug>.md in the vault as a fallback so it isn't lost, tell the owner you saved it locally but couldn't reach their developer's queue, and suggest running /setup to reconnect GitHub.