9d739dfa5d
- All gsdDir/gsdRoot/gsdHome → sfDir/sfRootDir/sfHome - GSDWorkspace* → SFWorkspace* interfaces - bootstrapGsdProject → bootstrapProject - runGSDDoctor → runSFDoctor - GsdClient → SfClient, gsd-client.ts → sf-client.ts - .gsd/ → .sf/ in all tests, docs, docker, native, vscode - Auto-migration: headless detects .gsd/ → renames to .sf/ - Deleted gsd-phase-state.ts backward-compat re-export - Renamed bin/gsd-from-source → bin/sf-from-source - Updated mintlify docs, github workflows, docker configs
83 lines
2.8 KiB
YAML
83 lines
2.8 KiB
YAML
name: Feature request
|
|
description: Propose a new capability or improvement for SF.
|
|
title: "[Feature]: "
|
|
labels:
|
|
- enhancement
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Help us evaluate this request with concrete use cases, constraints, and tradeoffs.
|
|
|
|
- type: textarea
|
|
id: summary
|
|
attributes:
|
|
label: Summary
|
|
description: One sentence describing the requested capability.
|
|
placeholder: Add a command to inspect queued milestones without entering auto-mode.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem to solve
|
|
description: What user pain this solves and why the current behavior is insufficient.
|
|
placeholder: I can queue work, but I cannot review it quickly from the CLI without opening project files.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposed_solution
|
|
attributes:
|
|
label: Proposed solution
|
|
description: Describe the desired behavior, UX, CLI shape, or API as specifically as you can.
|
|
placeholder: Add `/sf queue list` that renders queued milestones with IDs, status, and created timestamps.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives considered
|
|
description: Other approaches considered and why they are weaker.
|
|
placeholder: Reading `.sf/QUEUE.md` manually works, but it is slower and harder to parse during terminal workflows.
|
|
|
|
- type: textarea
|
|
id: use_cases
|
|
attributes:
|
|
label: Use cases
|
|
description: Give one or more concrete scenarios where this would help.
|
|
placeholder: |
|
|
- Reviewing queued work before starting auto-mode
|
|
- CI or automation scripts that need a concise queue summary
|
|
- Triage sessions across multiple milestones
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: impact
|
|
attributes:
|
|
label: Impact
|
|
description: Explain who is affected, urgency, frequency, and practical consequence.
|
|
placeholder: |
|
|
Affected: users running multi-milestone project flows
|
|
Severity: medium
|
|
Frequency: several times per week
|
|
Consequence: extra manual steps and slower triage
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: evidence
|
|
attributes:
|
|
label: Evidence or prior art
|
|
description: Comparable tools, links, examples, screenshots, logs, or metrics.
|
|
placeholder: Similar queue-list commands exist in ..., or here is an example of the current manual workflow.
|
|
|
|
- type: textarea
|
|
id: additional_information
|
|
attributes:
|
|
label: Additional information
|
|
description: Extra constraints, compatibility concerns, implementation hints, or references.
|
|
placeholder: Must remain compatible with existing `.sf/QUEUE.md` structure.
|