name: ✨ Feature Request
description: Propose new functionality or an improvement.
title: "[Feature]: "
labels: ["enhancement"]
body:
- type: markdown
attributes:
value: |
Describe the problem and the desired outcome. Clear scope and acceptance criteria let a human or AI agent implement this correctly.
- type: textarea
id: problem
attributes:
label: Problem / user story
description: What need does this serve? Prefer "As a <user> I want <goal> so that <reason>".
placeholder: As a user I want `spm` to support skills from a subdirectory of a git repo so that I can vendor a single skill from a monorepo.
validations:
required: true
- type: textarea
id: solution
attributes:
label: Proposed solution
description: What you think should be built. Rough is fine.
validations:
required: true
- type: textarea
id: scope
attributes:
label: Scope
description: Bound the work. Prevents scope creep for any implementer, human or agent.
placeholder: |
In scope:
-
Out of scope:
-
validations:
required: true
- type: textarea
id: affected-areas
attributes:
label: Affected areas
description: Files or modules likely to change.
placeholder: |
- src/cli.rs (new flag / command)
- src/manifest.rs (ai.json field)
- schema/ai.schema.json (schema update)
validations:
required: false
- type: textarea
id: acceptance
attributes:
label: Acceptance criteria
description: Testable checkboxes defining "done".
placeholder: |
- [ ] New subdirectory field accepted in ai.json and validated by the schema
- [ ] Only the named subdirectory is materialized for each target
- [ ] Empty / missing subdirectory handled with a clear error
- [ ] Tests in tests/cli.rs cover the new behavior
validations:
required: true