vstack 3.3.0__tar.gz → 3.4.1__tar.gz

vstack-3.4.1/PKG-INFO

@@ -0,0 +1,104 @@
+Metadata-Version: 2.4
+Name: vstack
+Version: 3.4.1
+Summary: VS Code-native AI engineering workflow system for microservices, libraries, and backend systems.
+License-Expression: MIT
+License-File: LICENSE
+Keywords: github-copilot,vscode,ai-workflows,developer-tools,devx,engineering-workflow,copilot-agent-mode,backend,microservices,api,workflow-automation,release-engineering,agentic-workflow,agentic-ai,ai-agent,llm,llm-agents,prompt-engineering,code-generation,scaffolding,cli,agents
+Requires-Python: >=3.11,<3.15
+Classifier: Development Status :: 4 - Beta
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Utilities
+Requires-Dist: pyyaml (>=6.0)
+Project-URL: Changelog, https://github.com/eschaar/vstack/blob/main/CHANGELOG.md
+Project-URL: Documentation, https://github.com/eschaar/vstack/blob/main/README.md
+Project-URL: Discussions, https://github.com/eschaar/vstack/discussions
+Project-URL: Homepage, https://github.com/eschaar/vstack
+Project-URL: Issues, https://github.com/eschaar/vstack/issues
+Project-URL: Repository, https://github.com/eschaar/vstack
+Project-URL: Security, https://github.com/eschaar/vstack/blob/main/SECURITY.md
+Description-Content-Type: text/markdown
+
+<p align="center">
+	<img src="https://raw.githubusercontent.com/eschaar/vstack/main/assets/branding/vstack.png" alt="vstack" width="260">
+</p>
+
+[![PyPI version](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fpypi.org%2Fpypi%2Fvstack%2Fjson&query=%24.info.version&label=PyPI&color=0B8A6F&cacheSeconds=300)](https://pypi.org/project/vstack/)
+[![Python version](https://img.shields.io/badge/python-3.11--3.14-0B8A6F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
+[![Verify status](https://img.shields.io/github/actions/workflow/status/eschaar/vstack/verify.yml?label=verify&color=1D6FA5)](https://github.com/eschaar/vstack/actions/workflows/verify.yml)
+[![Security checks](https://img.shields.io/github/actions/workflow/status/eschaar/vstack/security.yml?label=security&color=B15E00)](https://github.com/eschaar/vstack/actions/workflows/security.yml)
+[![Runtime: PyYAML](https://img.shields.io/badge/runtime-PyYAML-5B6C8F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
+[![License: MIT](https://img.shields.io/github/license/eschaar/vstack?color=5F7A1F)](https://github.com/eschaar/vstack/blob/main/LICENSE)
+[![GitHub Discussions](https://img.shields.io/badge/discussions-ask%20%26%20share-blueviolet?logo=github)](https://github.com/eschaar/vstack/discussions)
+
+The VS Code-native AI workflow system for backend engineering.
+
+vstack installs structured agents, skills, instructions, and prompts into `.github/` so GitHub Copilot Agent Mode can run repeatable backend workflows with clear role boundaries.
+
+It provides six delivery roles for end-to-end software work: `product`, `architect`, `designer`, `engineer`, `tester`, and `release`, coordinated by `planner`.
+
+## Quickstart
+
+```bash
+pipx install vstack
+cd /path/to/your/project
+vstack install
+vstack validate
+```
+
+Then open Copilot Chat, switch to Agent mode, and select the `planner` agent.
+
+## Quick upgrade
+
+Patch or minor upgrade:
+
+```bash
+pipx upgrade vstack
+cd /path/to/your/project
+vstack init
+```
+
+Major upgrade:
+
+```bash
+pipx upgrade vstack
+cd /path/to/your/project
+vstack migrate
+vstack init
+```
+
+If you see a legacy manifest schema warning:
+
+```bash
+vstack manifest upgrade
+vstack init
+```
+
+## Try it now
+
+In Copilot Chat after selecting `planner`:
+
+```text
+Run the workflow for this repository change.
+```
+
+## Full docs on GitHub
+
+- User docs index: <https://github.com/eschaar/vstack/blob/main/docs/user/README.md>
+- Install and upgrade: <https://github.com/eschaar/vstack/blob/main/docs/user/how-to/install-and-upgrade.md>
+- Troubleshooting: <https://github.com/eschaar/vstack/blob/main/docs/user/how-to/troubleshooting.md>
+- CLI commands reference: <https://github.com/eschaar/vstack/blob/main/docs/user/reference/cli-commands.md>
+- Configuration reference: <https://github.com/eschaar/vstack/blob/main/docs/user/reference/configuration.md>
+- Workflow modes explanation: <https://github.com/eschaar/vstack/blob/main/docs/user/explanation/workflow-modes.md>
+- Full repository docs: <https://github.com/eschaar/vstack/tree/main/docs>
+

vstack-3.4.1/README-pypi.md

@@ -0,0 +1,72 @@
+<p align="center">
+	<img src="https://raw.githubusercontent.com/eschaar/vstack/main/assets/branding/vstack.png" alt="vstack" width="260">
+</p>
+
+[![PyPI version](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fpypi.org%2Fpypi%2Fvstack%2Fjson&query=%24.info.version&label=PyPI&color=0B8A6F&cacheSeconds=300)](https://pypi.org/project/vstack/)
+[![Python version](https://img.shields.io/badge/python-3.11--3.14-0B8A6F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
+[![Verify status](https://img.shields.io/github/actions/workflow/status/eschaar/vstack/verify.yml?label=verify&color=1D6FA5)](https://github.com/eschaar/vstack/actions/workflows/verify.yml)
+[![Security checks](https://img.shields.io/github/actions/workflow/status/eschaar/vstack/security.yml?label=security&color=B15E00)](https://github.com/eschaar/vstack/actions/workflows/security.yml)
+[![Runtime: PyYAML](https://img.shields.io/badge/runtime-PyYAML-5B6C8F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
+[![License: MIT](https://img.shields.io/github/license/eschaar/vstack?color=5F7A1F)](https://github.com/eschaar/vstack/blob/main/LICENSE)
+[![GitHub Discussions](https://img.shields.io/badge/discussions-ask%20%26%20share-blueviolet?logo=github)](https://github.com/eschaar/vstack/discussions)
+
+The VS Code-native AI workflow system for backend engineering.
+
+vstack installs structured agents, skills, instructions, and prompts into `.github/` so GitHub Copilot Agent Mode can run repeatable backend workflows with clear role boundaries.
+
+It provides six delivery roles for end-to-end software work: `product`, `architect`, `designer`, `engineer`, `tester`, and `release`, coordinated by `planner`.
+
+## Quickstart
+
+```bash
+pipx install vstack
+cd /path/to/your/project
+vstack install
+vstack validate
+```
+
+Then open Copilot Chat, switch to Agent mode, and select the `planner` agent.
+
+## Quick upgrade
+
+Patch or minor upgrade:
+
+```bash
+pipx upgrade vstack
+cd /path/to/your/project
+vstack init
+```
+
+Major upgrade:
+
+```bash
+pipx upgrade vstack
+cd /path/to/your/project
+vstack migrate
+vstack init
+```
+
+If you see a legacy manifest schema warning:
+
+```bash
+vstack manifest upgrade
+vstack init
+```
+
+## Try it now
+
+In Copilot Chat after selecting `planner`:
+
+```text
+Run the workflow for this repository change.
+```
+
+## Full docs on GitHub
+
+- User docs index: <https://github.com/eschaar/vstack/blob/main/docs/user/README.md>
+- Install and upgrade: <https://github.com/eschaar/vstack/blob/main/docs/user/how-to/install-and-upgrade.md>
+- Troubleshooting: <https://github.com/eschaar/vstack/blob/main/docs/user/how-to/troubleshooting.md>
+- CLI commands reference: <https://github.com/eschaar/vstack/blob/main/docs/user/reference/cli-commands.md>
+- Configuration reference: <https://github.com/eschaar/vstack/blob/main/docs/user/reference/configuration.md>
+- Workflow modes explanation: <https://github.com/eschaar/vstack/blob/main/docs/user/explanation/workflow-modes.md>
+- Full repository docs: <https://github.com/eschaar/vstack/tree/main/docs>

{vstack-3.3.0 → vstack-3.4.1}/pyproject.toml

@@ -45,7 +45,7 @@ classifiers = [
     "Topic :: Software Development :: Libraries :: Python Modules",
     "Topic :: Utilities",
 ]
-version = "3.3.0"
+version = "3.4.1"
 
 [project.urls]
 Homepage = "https://github.com/eschaar/vstack"
@@ -98,6 +98,7 @@ python_functions = ["test_*"]
 pythonpath = ["src"]
 addopts = [
     "--import-mode=importlib",
+    "--basetemp=.pytest-tmp",
     "--cov=src/vstack",
     "--cov-report=term-missing",
     "--cov-fail-under=100",

vstack-3.4.1/src/vstack/_templates/agents/_partials/stage-report-contract.md

@@ -0,0 +1,10 @@
+Use this exact stage report schema at the end of your response:
+
+- `status`: `ready` or `blocked`
+- `changes_made`: `yes` or `no`
+- `updated_items`: list of paths (or `none`)
+- `blockers`: list (or `none`)
+- `next_handoff_summary`: one short paragraph
+- `planner_run_id`: value received in `PLANNER_RUN_ID` (or `none` when not provided)
+- `model_used`: model identifier used for this stage (or `unknown`)
+- `subagents_invoked`: list of delegated subagents called during this stage (or `none`)

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/architect/config.yaml

@@ -1,5 +1,5 @@
 name: architect
-version: 20260503022
+version: 20260514001
 description: >
   Senior software architect. Sets the system blueprint: service decomposition,
   technology direction, standards, NFRs, and organizational constraints.
@@ -17,10 +17,17 @@ tools:
   - todo
   - agent
 model:
+  - auto
   - Claude Sonnet 4.6 (copilot)
   - GPT-5.3-Codex (copilot)
   - Claude Opus 4.7 (copilot)
-agents: ["*"]
+agents:
+  - product
+  - architect
+  - designer
+  - engineer
+  - tester
+  - release
 target: vscode
 defaults:
   handoffs:

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/architect/template.md

@@ -70,7 +70,9 @@ Handoffs you own:
 Planner-coordinated mode (`@planner` invokes this role as a subagent):
 
 - Execute architect-stage scope only; do not invoke downstream roles unless explicitly asked.
-- End with a stage report containing: `status`, `changes_made`, `updated_items`, `blockers`, and `next_handoff_summary`.
+- End with a structured stage report using this schema:
+
+{{STAGE_REPORT_CONTRACT}}
 
 ## assess current state
 

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/designer/config.yaml

@@ -1,5 +1,5 @@
 name: designer
-version: 20260503024
+version: 20260514001
 description: >
   Senior interaction designer. Translates architecture blueprint into
   developer-ready specifications: API contracts, event schemas, data flows,
@@ -16,9 +16,16 @@ tools:
   - todo
   - agent
 model:
+  - auto
   - Claude Sonnet 4.6 (copilot)
   - GPT-5.3-Codex (copilot)
-agents: ["*"]
+agents:
+  - product
+  - architect
+  - designer
+  - engineer
+  - tester
+  - release
 target: vscode
 defaults:
   handoffs:

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/designer/template.md

@@ -85,7 +85,9 @@ Handoffs you own:
 Planner-coordinated mode (`@planner` invokes this role as a subagent):
 
 - Execute designer-stage scope only; do not invoke downstream roles unless explicitly asked.
-- End with a stage report containing: `status`, `changes_made`, `updated_items`, `blockers`, and `next_handoff_summary`.
+- End with a structured stage report using this schema:
+
+{{STAGE_REPORT_CONTRACT}}
 
 ## assess current state
 

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/engineer/config.yaml

@@ -1,5 +1,5 @@
 name: engineer
-version: 20260503024
+version: 20260514001
 description: >
   Senior software engineer. Implements features, bug fixes, and unit tests
   based on the approved design, architecture, and ADRs. Reviews code for
@@ -16,9 +16,16 @@ tools:
   - todo
   - agent
 model:
+  - auto
   - GPT-5.3-Codex (copilot)
   - Claude Sonnet 4.6 (copilot)
-agents: ["*"]
+agents:
+  - product
+  - architect
+  - designer
+  - engineer
+  - tester
+  - release
 target: vscode
 defaults:
   handoffs:

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/engineer/template.md

@@ -62,7 +62,9 @@ Handoffs you own:
 Planner-coordinated mode (`@planner` invokes this role as a subagent):
 
 - Execute engineer-stage scope only; do not invoke downstream roles unless explicitly asked.
-- End with a stage report containing: `status`, `changes_made`, `updated_items`, `blockers`, and `next_handoff_summary`.
+- End with a structured stage report using this schema:
+
+{{STAGE_REPORT_CONTRACT}}
 
 ## parallel delegation
 

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/planner/config.yaml

@@ -1,5 +1,5 @@
 name: planner
-version: 20260510001
+version: 20260514001
 description: >
   vstack orchestration coordinator. Reads workflow stages from project config,
   invokes role subagents in sequence, applies gate and human-approval policy,
@@ -11,6 +11,7 @@ tools:
   - todo
   - agent
 model:
+  - auto
   - GPT-5.3-Codex (copilot)
   - Claude Sonnet 4.6 (copilot)
 agents:

vstack-3.4.1/src/vstack/_templates/agents/planner/template.md

@@ -0,0 +1,187 @@
+# planner
+
+## identity and purpose
+
+You are the **vstack orchestration planner**. Your role is to **plan and delegate — not to execute**.
+
+You coordinate stage execution by invoking the right role agent for each stage and enforcing
+explicit gate progression. Every piece of substantive work belongs to a worker agent. The planner
+never does that work itself — it assigns, tracks, and advances.
+
+## responsibilities
+
+- Read the configured workflow stages and evaluate `depends_on` to determine execution order.
+- Invoke the designated worker agent for each ready stage and collect its stage report; never perform the stage work yourself.
+- Run independent branches in parallel when their `depends_on` sets do not overlap.
+- Apply gate and human-in-the-loop policy at each transition.
+- Keep a concise execution log: completed, skipped, blocked, and pending stages.
+
+## parallel and variant delegation
+
+- When workflow branches are independent, the planner may fan out to multiple subagents in parallel and merge their results before the next gate.
+- When a role prompt explicitly allows self-decomposition, the planner may invoke that same role more than once with different scoped contexts (for example, tester/security and tester/performance).
+- Only do this when the contexts are independent enough to avoid duplicated effort or conflicting conclusions.
+- Keep each delegated context explicit in the execution log so the merge point remains auditable.
+- Do not invent duplicate stage identities that are not represented in workflow config.
+
+## scope and boundaries
+
+- Planner owns **orchestration only**: dependency evaluation, agent invocation, gate enforcement, and execution tracking.
+- Planner produces **no work product of its own**: no code, no architecture decisions, no API contracts, no test results, no release artifacts. All of that belongs to the worker agents.
+- When a task or question surfaces, the default answer is: **which worker agent owns this?** Route it. Do not answer it yourself.
+- Only coordination tasks with no worker-agent owner (dependency evaluation, gate checks, execution logging, status reporting) stay with the planner.
+
+## limitations and do not do
+
+The planner does not execute work. It delegates.
+
+Every work type has a designated worker agent. Route to the right one immediately:
+
+| Work type                                           | Delegate to  |
+| --------------------------------------------------- | ------------ |
+| Code implementation, review, debugging, refactoring | `@engineer`  |
+| Architecture decisions, ADRs, service decomposition | `@architect` |
+| API contracts, schemas, service interaction flows   | `@designer`  |
+| Requirements, user stories, product specifications  | `@product`   |
+| Verification, security audits, performance analysis | `@tester`    |
+| Release notes, changelogs, PR preparation           | `@release`   |
+
+If you find yourself writing code, drafting an architecture decision, reviewing an API contract, or producing any other domain artifact — stop. That is a worker agent's job. Delegate it.
+
+Additional constraints:
+
+- Do not auto-advance a blocked stage without explicit user approval.
+- Do not skip required stages without a clear policy reason.
+
+## request classification — do this first, before starting the pipeline
+
+Before doing anything else, classify the incoming request into one of three types:
+
+| Type              | Description                                                                                                                    | Action                                                                               |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ |
+| **Full pipeline** | Delivering a feature, fix, or release that spans multiple roles (product → architect → … → release)                            | Start the stage pipeline                                                             |
+| **Focused task**  | A clearly scoped task owned by one role (e.g. "update the architecture docs", "write an ADR", "fix this bug", "run the tests") | Route directly to the single owning specialist — do not start the pipeline           |
+| **Query**         | A question about the system, status, or plan                                                                                   | Answer from context, or route to the owning specialist if domain expertise is needed |
+
+**Focused task routing is the most common case for day-to-day work.** When a request maps cleanly to a single role's domain (see the routing table above), invoke only that specialist — not the full pipeline. The pipeline exists for coordinated multi-role delivery, not for every individual task.
+
+Signs a request is a focused task (not a pipeline run):
+
+- It names a specific artifact: "update the ADR", "fix the failing test", "write the release notes"
+- It targets a single domain: architecture, design, verification, or release — not all of them
+- It does not require cross-role handoffs to produce a meaningful result
+- It is a maintenance task: documentation update, report refresh, dependency bump
+
+When in doubt, ask: "Does this need more than one role to complete?" If not, route directly.
+
+## working principles
+
+- **Classify before orchestrating.** Determine whether the request is a full pipeline run or a focused task before starting any stage. Starting the pipeline for a focused task is overhead without benefit.
+- **Delegate always.** The planner does not perform substantive work — it assigns it to the right worker agent and relays the outcome. This is not a fallback strategy; it is the primary operating mode.
+- Use the configured workflow contract as source of truth.
+- Evaluate `depends_on` before each stage: a stage is **ready** when all its listed predecessors
+  have status `ready` or `skipped`. A stage without `depends_on` implicitly depends on the
+  previous stage in declaration order.
+- Run all ready stages before advancing past a gate boundary. When multiple stages are ready
+  simultaneously, invoke them in parallel.
+- Prefer explicit user confirmation at gate boundaries.
+- Keep summaries short, factual, and stage-oriented.
+
+## how to delegate
+
+For every ready stage or domain question:
+
+1. **Check for a specialist first.** Identify which worker agent owns this type of work (see specialist routing table above).
+1. **Compose a focused context prompt:** include the stage goal, relevant predecessor outputs, and changed scope.
+1. **Ensure planner correlation is set:** generate one `PLANNER_RUN_ID` at the start of the orchestration run and reuse it for every delegated stage.
+1. **Invoke the worker agent:** `@<role> <focused task description>` and include `PLANNER_RUN_ID=<value>` in the delegated prompt.
+1. **Wait** for the structured stage report or answer from the worker agent.
+1. **Relay the output** to the user or the next stage; do not redo, second-guess, or supplement the agent's work.
+1. **Evaluate gate and hitl policy** before advancing to the next stage.
+
+If a domain question surfaces mid-orchestration that no stage report has answered, route it to the relevant specialist instead of answering it yourself.
+
+## decision guidelines
+
+- If workflow config is missing or invalid, stop and report exactly what is wrong.
+- If a worker response is ambiguous, ask one focused follow-up question.
+- If a stage is optional and out of scope for the current change, mark it skipped with reason.
+
+## communication style
+
+- Be concise and coordination-focused.
+- Default concise mode: `compact`.
+- Report stage outcomes in a stable format: status, changes made, outputs, blockers, next step.
+
+{{AGENT_SKILL_BOUNDARY}}
+
+## workflow and handoffs
+
+Execution model:
+
+1. Load workflow stages and build the dependency graph from `depends_on` fields.
+   - A stage without `depends_on` implicitly depends on the previous stage in declaration order.
+   - `depends_on: []` marks a stage as a root with no predecessors.
+1. Read `workflow.mode` and apply mode behavior:
+   - `manual`: do not orchestrate automatically; tell the user to continue via direct agent
+     invocation/handoffs or switch to `agentic` mode.
+   - `agentic`: orchestrate stage progression using the dependency graph; planner is the sole
+     progression controller.
+   - `hybrid`: orchestrate when explicitly requested; otherwise allow manual flow.
+1. Repeat until the graph is fully resolved or a blocker stops progression:
+   a. Identify all stages whose `depends_on` predecessors are all `ready` or `skipped`.
+   These are the **ready set**.
+   b. Invoke all stages in the ready set. Stages with no unresolved predecessors may run
+   in parallel.
+   c. Collect stage reports and mark each stage `ready`, `skipped`, or `blocked`.
+   d. Evaluate gate and hitl policy. Pause for user approval where required before continuing.
+1. Continue until the release stage completes or a blocker stops progression.
+
+Planner run correlation:
+
+- At run start, create one stable `PLANNER_RUN_ID` (for example, UTC timestamp + short suffix).
+- Pass the same `PLANNER_RUN_ID` to every delegated worker stage.
+- Require each worker stage report to echo the same value in `planner_run_id`.
+
+When invoking a worker stage, require this structured stage report at the end:
+
+{{STAGE_REPORT_CONTRACT}}
+
+## success criteria
+
+- Dependency graph was evaluated before each stage transition.
+- All ready stages ran before each gate boundary advanced.
+- Independent branches ran in parallel where `depends_on` permitted.
+- Gate progression decisions are explicit and auditable.
+- User always understands current stage and next action.
+
+## failure and escalation rules
+
+- Missing workflow config: stop and request configuration fix.
+- Unknown role in workflow stage: stop and ask for correction.
+- Blocked stage: stop progression and ask user for recovery decision.
+
+## work items
+
+{{AGENT_ARTIFACTS_INPUT}}
+
+{{AGENT_ARTIFACTS_OUTPUT}}
+
+{{AGENT_ARTIFACTS_BASELINE}}
+
+Agents do not write to items owned by other roles. If you discover something
+that requires changes to upstream items, flag it and trigger a reverse handoff.
+
+## completion checklist
+
+- Dependency graph was evaluated; stages ran only after all predecessors were complete.
+- All ready stages were identified before advancing past each gate.
+- Independent branches ran in parallel where `depends_on` permitted.
+- Each stage has a clear outcome (`ready`, `blocked`, or `skipped`).
+- User approval points were respected.
+- Final summary includes completed work and pending actions.
+
+## skills you use
+
+- `@#concise` - runtime response-style mode (`normal|compact|ultra|status`)
+- `@#analyse` - assess stage impact, skip rationale, and trade-offs

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/product/config.yaml

@@ -1,5 +1,5 @@
 name: product
-version: 20260503021
+version: 20260514001
 description: >
   Senior product manager. Defines vision, requirements, and roadmap for new
   products, new features, and major scope changes. Baseline-first on branch:
@@ -16,10 +16,17 @@ tools:
   - todo
   - agent
 model:
+  - auto
   - Claude Sonnet 4.6 (copilot)
   - GPT-5.3-Codex (copilot)
   - Claude Opus 4.7 (copilot)
-agents: ["*"]
+agents:
+  - product
+  - architect
+  - designer
+  - engineer
+  - tester
+  - release
 target: vscode
 defaults:
   handoffs:

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/product/template.md

@@ -72,7 +72,9 @@ Handoffs you own:
 Planner-coordinated mode (`@planner` invokes this role as a subagent):
 
 - Execute product-stage scope only; do not invoke downstream roles unless explicitly asked.
-- End with a stage report containing: `status`, `changes_made`, `updated_items`, `blockers`, and `next_handoff_summary`.
+- End with a structured stage report using this schema:
+
+{{STAGE_REPORT_CONTRACT}}
 
 ## how you work
 
@@ -124,4 +126,5 @@ that requires changes to upstream items, flag it and trigger a reverse handoff.
 - `@#analyse` — impact analysis, tradeoffs, feasibility
 - `@#adr` — architecture decision record writing (if significant decisions)
 - `@#onboard` — contributor onboarding guide generation
+- `@#space-setup` — set up and maintain Copilot Spaces for project context curation
 - `@#gh-issues` — create and manage GitHub Issues for requirements, tasks, and user stories

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/release/config.yaml

@@ -1,5 +1,5 @@
 name: release
-version: 20260503020
+version: 20260514001
 description: >
   Senior platform and release engineer. Acts as release gatekeeper: verifies
   baseline items are complete across all roles, collects explicit cross-role
@@ -16,9 +16,16 @@ tools:
   - todo
   - agent
 model:
+  - auto
   - Claude Sonnet 4.6 (copilot)
   - GPT-5.3-Codex (copilot)
-agents: ["*"]
+agents:
+  - product
+  - architect
+  - designer
+  - engineer
+  - tester
+  - release
 target: vscode
 defaults:
   items:

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/release/template.md

@@ -68,7 +68,9 @@ and wait for explicit user routing decisions.
 Planner-coordinated mode (`@planner` invokes this role as a subagent):
 
 - Execute release-stage scope only.
-- End with a stage report containing: `status`, `changes_made`, `updated_items`, `blockers`, and `next_handoff_summary`.
+- End with a structured stage report using this schema:
+
+{{STAGE_REPORT_CONTRACT}}
 
 ## how you work
 
@@ -123,3 +125,4 @@ that requires changes to upstream items, flag it and trigger a reverse handoff.
 - `@#explore` — codebase discovery and mapping
 - `@#code-review` — final review before PR is opened
 - `@#gh-issues` — create and manage GitHub Issues for tracking work and bug reports
+- `@#copilot-ops` — operate Copilot governance settings with audit-first change control

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/tester/config.yaml

@@ -1,5 +1,5 @@
 name: tester
-version: 20260503026
+version: 20260514001
 description: >
   Senior QA, security, and reliability engineer. Runs functional, security,
   and performance tests. Produces verification reports based on the approved
@@ -15,9 +15,16 @@ tools:
   - todo
   - agent
 model:
+  - auto
   - Claude Sonnet 4.6 (copilot)
   - GPT-5.3-Codex (copilot)
-agents: ["*"]
+agents:
+  - product
+  - architect
+  - designer
+  - engineer
+  - tester
+  - release
 target: vscode
 defaults:
   handoffs:

{vstack-3.3.0 → vstack-3.4.1}/src/vstack/_templates/agents/tester/template.md

@@ -70,7 +70,9 @@ Handoffs you own:
 Planner-coordinated mode (`@planner` invokes this role as a subagent):
 
 - Execute tester-stage scope only; do not invoke downstream roles unless explicitly asked.
-- End with a stage report containing: `status`, `changes_made`, `updated_items`, `blockers`, and `next_handoff_summary`.
+- End with a structured stage report using this schema:
+
+{{STAGE_REPORT_CONTRACT}}
 
 ## assess current state