chore: import upstream snapshot with attribution

This commit is contained in:
wehub-resource-sync
2026-07-13 11:57:40 +08:00
commit 923a61929d
462 changed files with 139124 additions and 0 deletions
@@ -0,0 +1,22 @@
# Business Analyst bundle
A role bundle for business analysts working in a Spec-Driven Development flow:
requirements elicitation, traceability, and acceptance criteria.
## What it installs
- **Extension** `agent-context` — keeps the agent context file in sync.
- **Preset** `requirements-elicitation` (priority 10, append) — elicitation and
analysis command set.
- **Steps** `capture-requirements`, `trace-acceptance-criteria`.
- **Workflow** `requirements-to-spec` — turns captured requirements into a spec.
This bundle is **integration-agnostic**: it inherits the project's active
integration.
## Usage
```bash
specify bundle validate --path examples/bundles/business-analyst
specify bundle build --path examples/bundles/business-analyst --output dist/
```
@@ -0,0 +1,33 @@
schema_version: "1.0"
bundle:
id: "business-analyst"
name: "Business Analyst"
version: "1.0.0"
role: "business-analyst"
description: "Spec-Driven Development setup for business analysts: requirements elicitation, traceability, and acceptance criteria."
author: "spec-kit-examples"
license: "MIT"
requires:
speckit_version: ">=0.9.0"
tools: []
mcp: []
provides:
extensions:
- id: "agent-context"
version: "1.0.0"
presets:
- id: "requirements-elicitation"
version: "1.0.0"
priority: 10
strategy: "append"
steps:
- id: "capture-requirements"
- id: "trace-acceptance-criteria"
workflows:
- id: "requirements-to-spec"
version: "1.0.0"
tags: ["requirements", "traceability", "analysis"]
+22
View File
@@ -0,0 +1,22 @@
# Developer bundle
A role bundle for developers practicing Spec-Driven Development: implementation
planning, task breakdown, and code review.
## What it installs
- **Extension** `agent-context` — keeps the agent context file in sync.
- **Preset** `implementation-planning` (priority 10, append) — implementation
planning command set.
- **Steps** `plan-implementation`, `break-down-tasks`.
- **Workflow** `spec-to-implementation` — drives a spec through to code.
This bundle is **integration-agnostic**: it inherits the project's active
integration.
## Usage
```bash
specify bundle validate --path examples/bundles/developer
specify bundle build --path examples/bundles/developer --output dist/
```
+33
View File
@@ -0,0 +1,33 @@
schema_version: "1.0"
bundle:
id: "developer"
name: "Developer"
version: "1.0.0"
role: "developer"
description: "Spec-Driven Development setup for developers: implementation planning, task breakdown, and code review."
author: "spec-kit-examples"
license: "MIT"
requires:
speckit_version: ">=0.9.0"
tools: []
mcp: []
provides:
extensions:
- id: "agent-context"
version: "1.0.0"
presets:
- id: "implementation-planning"
version: "1.0.0"
priority: 10
strategy: "append"
steps:
- id: "plan-implementation"
- id: "break-down-tasks"
workflows:
- id: "spec-to-implementation"
version: "1.0.0"
tags: ["development", "implementation", "code-review"]
@@ -0,0 +1,22 @@
# Product Manager bundle
A role bundle that prepares a Spec Kit project for product managers driving
Spec-Driven Development: discovery, specification, and roadmap planning.
## What it installs
- **Extension** `agent-context` — keeps the agent context file in sync.
- **Preset** `product-discovery` (priority 10, append) — discovery-oriented
command set.
- **Steps** `draft-spec`, `review-spec` — specification authoring steps.
- **Workflow** `spec-to-roadmap` — turns an approved spec into a roadmap.
This bundle is **integration-agnostic**: it inherits whatever integration the
project already uses (e.g. `copilot`, `claude`).
## Usage
```bash
specify bundle validate --path examples/bundles/product-manager
specify bundle build --path examples/bundles/product-manager --output dist/
```
@@ -0,0 +1,35 @@
schema_version: "1.0"
bundle:
id: "product-manager"
name: "Product Manager"
version: "1.0.0"
role: "product-manager"
description: "Spec-Driven Development setup for product managers: discovery, specification, and roadmap workflows."
author: "spec-kit-examples"
license: "MIT"
requires:
speckit_version: ">=0.9.0"
tools: []
mcp: []
# Agnostic bundle: inherits the project's active integration.
provides:
extensions:
- id: "agent-context"
version: "1.0.0"
presets:
- id: "product-discovery"
version: "1.0.0"
priority: 10
strategy: "append"
steps:
- id: "draft-spec"
- id: "review-spec"
workflows:
- id: "spec-to-roadmap"
version: "1.0.0"
tags: ["product", "discovery", "roadmap"]
@@ -0,0 +1,23 @@
# Security Researcher bundle
A role bundle for security researchers practicing Spec-Driven Development:
threat modeling, security review, and compliance.
## What it installs
- **Extension** `agent-context` — keeps the agent context file in sync.
- **Preset** `security-compliance` (priority 5, append) — security and
compliance command set; presets apply in ascending priority order, so this
low number (5) places it ahead of higher-numbered presets in the stack.
- **Steps** `threat-model`, `security-review`.
- **Workflow** `secure-sdd` — a security-first SDD workflow.
This bundle is **integration-agnostic**: it inherits the project's active
integration.
## Usage
```bash
specify bundle validate --path examples/bundles/security-researcher
specify bundle build --path examples/bundles/security-researcher --output dist/
```
@@ -0,0 +1,33 @@
schema_version: "1.0"
bundle:
id: "security-researcher"
name: "Security Researcher"
version: "1.0.0"
role: "security-researcher"
description: "Spec-Driven Development setup for security researchers: threat modeling, security review, and compliance checks."
author: "spec-kit-examples"
license: "MIT"
requires:
speckit_version: ">=0.9.0"
tools: []
mcp: []
provides:
extensions:
- id: "agent-context"
version: "1.0.0"
presets:
- id: "security-compliance"
version: "1.0.0"
priority: 5
strategy: "append"
steps:
- id: "threat-model"
- id: "security-review"
workflows:
- id: "secure-sdd"
version: "1.0.0"
tags: ["security", "compliance", "threat-modeling"]