@trieungoctam/speckit 0.3.5 → 0.4.0

package/docs/product-contract.md

@@ -5,11 +5,13 @@ Speckit owns the workflow contract for enterprise Agile + TDD development with a
 ## Speckit Owns
 
 - The `.speckit/` source of truth: config, rules, workflows, templates, generated artifacts.
-- The command surface: `init`, `doctor`, `validate`, `start`, `memory`, `permissions`, `session`, `shape`, `plan`, `context`, `quick`, `sync`, `triage`, `sprint`, `graph`, `next`, `ready`, `run`, `review`, `close`.
+- The command surface: `init`, `doctor`, `validate`, `start`, `memory`, `permissions`, `session`, `team`, `score`, `shape`, `plan`, `context`, `quick`, `sync`, `triage`, `sprint`, `graph`, `next`, `ready`, `run`, `review`, `close`.
 - The skill catalog and super-agent routing contract for phase-specific agent behavior.
 - IDE-specific initialization that installs the shared Speckit runtime plus only the selected IDE adapter when `--ide <name>` is provided.
 - The long-session contract: project memory, active session state, checkpoints, compaction summaries, and resume handoffs.
 - The workflow validation contract: phase order, core skills, super-agent routing, run prompt terms, and installed adapter prompt parity.
+- The enterprise team contract: Product Owner, Analyst, Architect, Developer, QA/Test, and Reviewer/Lead artifact ownership.
+- The runtime score contract: project and story health across workflow, team, session/context, graph, TDD, and review categories.
 - The TDD gate: code stories require red, green, and refactor evidence.
 - The adapter compiler for Claude Code, Codex, Antigravity, OpenCode, and Cursor.
 - The safety policy for destructive commands, secrets, production access, and review readiness.
@@ -26,7 +28,24 @@ Speckit owns the workflow contract for enterprise Agile + TDD development with a
 ## State Model
 
 ```text
-intake -> session -> memory-ready -> shaped -> planned -> sprint-ready -> context-ready -> synced -> graph-triaged -> ready-for-dev -> tests-red -> checkpointed -> running -> tests-green -> refactor -> compacted -> review-ready -> closed
+intake -> session -> memory-ready -> shaped -> planned -> sprint-ready -> context-ready -> synced -> graph-triaged -> team-status -> ready-for-dev -> tests-red -> checkpointed -> running -> tests-green -> refactor -> team-audit -> compacted -> review-ready -> closed
 ```
 
 Implementation starts only after `speckit ready <story>` passes. Review starts only after test evidence exists and the active session has a current checkpoint.
+
+## Team Artifact Model
+
+| Role | Owned Artifact |
+| --- | --- |
+| Product Owner | `Business Goal`, priority, success signal |
+| Analyst | `Acceptance Criteria`, `Edge Cases` |
+| Architect | `Implementation Scope`, `Architecture Notes` |
+| Developer | `Dev Agent Record`, `File List`, `Change Log` |
+| QA/Test | linked TDD evidence red, green, refactor sections |
+| Reviewer/Lead | `Review Evidence`, follow-ups, close readiness |
+
+`speckit team status` reports current ownership gaps. `speckit team audit` enforces the review gate. `speckit team handoff` records role transfer.
+
+## Runtime Score Model
+
+`speckit score` is a health signal, not a replacement for tests. It shows whether the project or story has enough durable workflow evidence to be understandable, reviewable, and handoff-ready.

package/docs/project-changelog.md

@@ -1,5 +1,36 @@
 # Project Changelog
 
+## 0.4.0 - 2026-05-11
+
+### Added
+
+- Added the Enterprise Team Workflow layer with generated team role, artifact ownership, working agreement, review gate, and handoff protocol files.
+- Added `speckit team status <story>` to show role-by-role artifact readiness for Product Owner, Analyst, Architect, Developer, QA/Test, and Reviewer/Lead.
+- Added `speckit team audit <story> [--json]` for review-gate blocking checks that can run in CI.
+- Added `speckit team handoff <story> --from <role> --to <role>` to create durable role handoff files.
+- Added `speckit score [story] [--json]` to score project or story workflow health for enterprise demos and CI health reporting.
+
+### Changed
+
+- Story templates and generated quick/plan stories now include business goal, priority, edge cases, implementation scope, architecture notes, Dev Agent Record, File List, and Change Log sections for team traceability.
+- `.beads/` is ignored as runtime graph mirror state.
+
+### Quality
+
+- Added enterprise team workflow tests for generated files, status, audit, and handoff behavior.
+
+## 0.3.6 - 2026-05-11
+
+### Added
+
+- Added ANSI color rendering for interactive CLI and TUI output, including setup prompts, init summaries, doctor checks, graph setup, readiness, validation, sync, and help headers.
+- Added `SPECKIT_COLOR=1` / `FORCE_COLOR` support for demos and snapshots, with `NO_COLOR` / `SPECKIT_COLOR=0` opt-out support.
+
+### Quality
+
+- Added color helper regression tests.
+- JSON output remains uncolored for automation.
+
 ## 0.3.5 - 2026-05-11
 
 ### Added

package/docs/release-checklist.md

@@ -6,12 +6,16 @@ Before publishing Speckit:
 - [x] `npm run lint` passes.
 - [x] `npm test` passes.
 - [x] `bin/speckit init --ide all` works in a temporary directory.
+- [x] `speckit init --enterprise --ide all` creates `.speckit/team/*`.
+- [x] `speckit team status|audit|handoff` has test coverage.
+- [x] `speckit score [story] --json` has test coverage.
 - [x] `npm pack --dry-run` includes only package-safe files.
 - [x] `package.json` name is `@trieungoctam/speckit` and `publishConfig.access` is `public`.
 - [x] README uses `npx @trieungoctam/speckit@latest`.
 - [x] Adapter output paths match `docs/adapters.md`.
 - [x] Cursor output uses `.cursor/rules/*.mdc`, not `.cursorrules`.
 - [x] `speckit next` only invokes `bv --robot-*`.
+- [x] `.beads/` runtime mirror files are ignored by git.
 - [ ] License and attribution review is complete for Speckit, Speckit Method, and Beads Viewer inspiration.
 - [x] README quickstart is accurate.
 - [x] No secrets, local credentials, or generated private data are included.

package/docs/spec-quality-gates.md

@@ -29,6 +29,8 @@ Every phase must link to the next durable artifact.
 | context | story | context pack | story -> context |
 | sync | story | graph task | story -> task id |
 | run | task/story | TDD evidence | task -> evidence |
+| team status | story + evidence | role readiness | role -> artifact |
+| team audit | story + evidence | gate report | blocker -> owner |
 | review | diff + evidence | review checklist | evidence -> review |
 | close | review | changelog / graph close | review -> close |
 
@@ -51,6 +53,30 @@ All supported IDEs must receive the same Speckit policy:
 - Session/context instructions
 - Graph command safety
 
+## Team Gate
+
+Enterprise stories must expose role-owned artifacts:
+
+- Product Owner: business goal, priority, success signal.
+- Analyst: testable acceptance criteria and edge cases.
+- Architect: implementation scope, constraints, and risks.
+- Developer: Dev Agent Record, File List, and Change Log.
+- QA/Test: red, green, and refactor evidence.
+- Reviewer/Lead: review outcome and follow-ups.
+
+Run:
+
+```bash
+speckit team status <story>
+speckit team audit <story> --json
+```
+
+## Score Gate
+
+`speckit score` gives a project-level health signal across workflow contract, team operating model, context/session, and graph sync. `speckit score <story>` gives a story-level signal across team readiness, developer trace, TDD evidence, and review gate.
+
+Use score as a rollout metric first. Only turn it into a hard CI threshold after the team agrees on acceptable minimums.
+
 ## Release Gate
 
 Before release:
@@ -67,4 +93,5 @@ For enterprise releases:
 ```bash
 speckit init --enterprise --ide all
 speckit doctor --deep --json
+speckit score --json
 ```

package/docs/system-architecture.md

@@ -14,6 +14,9 @@ bin/speckit
 - `src/commands/*`: command implementations with filesystem-safe outputs.
 - `src/core/managed-files.ts`: creates or updates only Speckit-managed files unless forced.
 - `src/core/scaffold.ts`: defines core `.speckit/` rules, workflows, and templates.
+- `src/core/team-scaffold.ts`: defines generated team operating model files for enterprise mode.
+- `src/core/team-report.ts`: evaluates role-owned story artifacts for team status, audit, and handoff.
+- `src/core/spec-score.ts`: calculates project and story workflow health scores.
 - `src/core/test-detection.ts`: detects project test commands for TDD evidence.
 - `src/adapters/*`: renders native IDE config and instruction packs.
 - `src/adapters/tool-checks.ts`: reports external tool availability.
@@ -21,7 +24,22 @@ bin/speckit
 ## Data Flow
 
 ```text
-user intent -> CLI command -> markdown/json artifact -> IDE adapter -> agent workflow
+user intent -> CLI command -> markdown/json artifact -> team/status gates -> IDE adapter -> agent workflow
 ```
 
 The CLI does not depend on external workflow runtimes. Beads and Beads Viewer are optional integrations discovered at runtime.
+
+## Enterprise Team Layer
+
+```text
+story + evidence
+  -> team-report
+  -> team status / audit / handoff
+  -> score
+```
+
+Team checks are artifact-based. They inspect story sections, linked TDD evidence, and generated team contracts instead of relying on chat history.
+
+## Score Layer
+
+`speckit score` aggregates health across workflow contract, team operating model, context/session state, and graph sync. `speckit score <story>` aggregates story health across team readiness, developer trace, TDD evidence, and review gate.

package/docs/team-workflow.md

@@ -0,0 +1,40 @@
+# Enterprise Team Workflow
+
+Speckit Enterprise Team Workflow makes agentic development visible across roles. A role can be a person, a pair, or an agent, but every role owns durable artifacts.
+
+## Roles
+
+| Role | Owns | Speckit Checks |
+| --- | --- | --- |
+| Product Owner | business goal, priority | `Business Goal`, `Priority` |
+| Analyst | acceptance criteria, edge cases | `Acceptance Criteria`, `Edge Cases` |
+| Architect | scope, constraints, risk | `Implementation Scope`, `Architecture Notes` |
+| Developer | implementation trace | `Dev Agent Record`, `File List`, `Change Log` |
+| QA/Test | TDD proof | linked evidence `Red`, `Green`, `Refactor` |
+| Reviewer/Lead | approval | `Review Evidence` |
+
+## Flow
+
+```bash
+speckit setup
+speckit quick "Add customer export"
+speckit context .speckit/stories/<story>.md
+speckit sync
+speckit team status .speckit/stories/<story>.md
+speckit ready .speckit/stories/<story>.md
+speckit run .speckit/stories/<story>.md
+speckit team handoff .speckit/stories/<story>.md --from dev --to qa
+speckit team audit .speckit/stories/<story>.md
+speckit score .speckit/stories/<story>.md
+```
+
+## Status Vs Audit
+
+- `speckit team status <story>` answers where the story is blocked across roles.
+- `speckit team audit <story>` answers whether the story can pass the review gate.
+- `speckit team handoff <story> --from <role> --to <role>` writes a durable handoff for long sessions or role transfer.
+- `speckit score <story>` gives a compact health score for team readiness, developer trace, TDD evidence, and review gate.
+
+## Enterprise Rule
+
+Do not advance a story by chat memory alone. Update the story, evidence, session, or handoff artifact first, then run team status or audit.

package/docs/use-cases.md

@@ -162,6 +162,10 @@ Best practices:
 Use after implementation and tests pass.
 
 ```bash
+speckit team status .speckit/stories/<story>.md
+speckit team audit .speckit/stories/<story>.md
+speckit score .speckit/stories/<story>.md
+speckit team handoff .speckit/stories/<story>.md --from dev --to reviewer
 speckit review
 speckit session compact
 speckit close .speckit/stories/<story>.md
@@ -172,6 +176,9 @@ speckit validate
 Best practices:
 
 - Review acceptance coverage before style or preference issues.
+- Use `team status` to locate the role and artifact blocking review.
+- Use `score <story>` as a quick executive summary before review or demo.
+- Use `team handoff` when responsibility moves between dev, QA, reviewer, or lead.
 - Check TDD evidence, session freshness, docs impact, and graph sync.
 - Close only after the story has current evidence and a clean handoff.
 - Sync after closing so downstream graph and sprint views are current.
@@ -187,12 +194,16 @@ npm run build
 npm test
 npx @trieungoctam/speckit@latest doctor --deep --json
 npx @trieungoctam/speckit@latest validate --json
+npx @trieungoctam/speckit@latest score --json
+npx @trieungoctam/speckit@latest team audit .speckit/stories/<story>.md --json
 ```
 
 Best practices:
 
 - Fail CI when `validate` returns `needs-attention`.
+- Use `score --json` as a non-blocking health metric until the team agrees on a threshold.
 - Require `doctor --deep` before release branches are merged.
+- Require `team audit` for stories that are ready for review or close.
 - Keep generated prompt files reviewed like source code.
 - Add new workflow phases only through the central contract and tests.
 - Do not allow IDE-specific prompts to drift from the shared Speckit contract.

package/docs/workflow-model.md

@@ -47,6 +47,26 @@ Outputs:
 - `.speckit/sprint/status.yaml`
 - `.speckit/sprint/plan.md`
 
+## Enterprise Team Lane
+
+Use when a story moves across product, analysis, architecture, development, QA, and review responsibilities.
+
+```bash
+speckit team status .speckit/stories/<story>.md
+speckit team handoff .speckit/stories/<story>.md --from dev --to qa
+speckit team audit .speckit/stories/<story>.md
+speckit score .speckit/stories/<story>.md
+```
+
+Outputs:
+
+- `.speckit/team/roles.md`
+- `.speckit/team/artifact-ownership.md`
+- `.speckit/team/review-gates.md`
+- `.speckit/team/handoffs/<handoff>.md`
+
+The team lane does not simulate people. It maps team responsibilities to durable artifacts so any person or agent can see which role is blocking the story.
+
 ## TDD Evidence Gate
 
 Each code story must record:
@@ -72,3 +92,14 @@ Long-running agent work must keep durable state outside chat history:
 `speckit sync` prepares both Speckit sync metadata and a Beads Viewer-compatible `.beads/beads.jsonl` mirror. `speckit graph triage|plan|insights` refreshes that mirror before invoking `bv --robot-*` from the project root, then falls back to local JSON if Beads Viewer is unavailable or still fails.
 
 Run `speckit graph setup` on a new machine to print Beads Viewer install commands, check `br`/`bd`/`bv`, and prepare `.beads/beads.jsonl`.
+
+## Runtime Score
+
+Use score as the compact executive summary of workflow health:
+
+```bash
+speckit score
+speckit score .speckit/stories/<story>.md
+```
+
+Project score checks workflow contract, team operating model, context/session, and graph sync. Story score checks team readiness, developer trace, TDD evidence, and review gate.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trieungoctam/speckit",
-  "version": "0.3.5",
+  "version": "0.4.0",
   "description": "Enterprise Agile + TDD workflow compiler for agentic IDEs.",
   "type": "module",
   "files": [