chore: Improve issue templates and add CLI feature request

Agent request: remove redundant name field (already in title),
broaden traction criteria to include fork activity and venture funding.

Cloud request: remove redundant name field (already in title),
consolidate API docs and billing into Additional Context.

New: CLI feature request template for spawn CLI improvements.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Sprite 2026-02-11 16:33:55 +00:00
parent 481daf9815
commit 7abfb045af
3 changed files with 69 additions and 58 deletions

View file

@ -0,0 +1,51 @@
name: CLI Feature Request
description: Suggest a new feature or improvement for the spawn CLI
title: "[CLI]: "
labels: ["cli", "enhancement", "needs-triage"]
body:
- type: markdown
attributes:
value: |
Thanks for the suggestion! Describe what you'd like the spawn CLI to do.
- type: textarea
id: description
attributes:
label: Feature Description
description: What should the CLI do? Be as specific as you can.
placeholder: |
spawn should support a `--dry-run` flag that shows what would
be provisioned without actually creating anything.
validations:
required: true
- type: textarea
id: use-case
attributes:
label: Use Case
description: Why do you need this? What problem does it solve?
placeholder: |
I want to preview costs before spinning up a server.
validations:
required: true
- type: textarea
id: proposed-ux
attributes:
label: Proposed UX
description: How would you expect to use this feature? Show example commands or workflows.
placeholder: |
$ spawn claude hetzner --dry-run
Would create: Hetzner CX22 in fsn1 (~$0.01/hr)
Run without --dry-run to proceed.
render: shell
validations:
required: false
- type: textarea
id: additional
attributes:
label: Additional Context
description: Any other details, mockups, or references to similar tools
validations:
required: false