@enterpriseai/cli 3.19.0 → 3.19.1

package/resources/gofer/copilot-prompts/7a_stakeholder_comms.prompt.md

@@ -1,516 +0,0 @@
----
-name: 7a_stakeholder_comms
-description: Generate stakeholder-facing communications: release notes, demo scripts, and change briefs.
-agent: copilot-workspace
-tools:
-  - Read
-  - Grep
-  - Glob
-  - Bash
-  - WebSearch
-argument-hint: feature-name-or-description
-gofer:
-  workflowProfile: standard
-  canonicalSource: .specify/commands/7a_stakeholder_comms.md
-  canonicalChecksum: 47031d30e808d88cd63abf3bd4e08ce4c14bb1fcec7fe08e0b1dc582d039a20f
-  metadataSource: scripts/generate-commands.ts
----
-
-## Workspace Preflight
-
-Before doing stage/helper work:
-
-1. Resolve the repository root.
-2. Check the core Gofer sentinels:
-   - `.specify/.gofer-version`
-   - `.specify/commands/0_gofer_start.md`
-   - `.specify/templates/spec-template.md`
-   - `.specify/templates/loop-contract-template.json`
-   - `.specify/templates/working-backwards-prfaq-template.md`
-   - `.specify/templates/business-owner-summary-template.md`
-   - `.specify/templates/cto-architecture-summary-template.md`
-   - `.specify/templates/ciso-security-summary-template.md`
-   - `.specify/templates/stakeholder-review-index-template.md`
-   - `.specify/scripts/bash/create-new-feature.sh`
-   - `.specify/scripts/node/parse-stage-command.mjs`
-   - `.specify/scripts/node/gofer-loop-audit.mjs`
-   - `.specify/scripts/hooks/post-tool-use.mjs`
-   - `.specify/scripts/powershell/install-optional-tools.ps1`
-   - `.specify/templates/gofer-model-policy.yaml`
-   - `.specify/memory/gofer-model-policy.yaml`
-   - `.specify/specs/`
-   - `.specify/memory/`
-3. Check host-specific repo-owned files when relevant:
-   - Claude: `AGENTS.md`, `CLAUDE.md`, `.claude/settings.json`
-   - Codex: `AGENTS.md`
-   - Copilot: `.github/copilot-instructions.md`
-   - VS Code extension mirrors Claude/Copilot/Gemini resources itself and should still keep the core scaffold healthy
-4. If the repo already has the workspace checker script, prefer running:
-   - `node .specify/scripts/node/gofer-workspace-check.mjs --host copilot --json`
-5. If the workspace is missing or stale, ask exactly:
-   - **"This repo is missing or stale for Gofer. Initialize/update it now?"**
-6. If the user says yes, run the Gofer workspace bootstrap helper and then resume this command from the top.
-7. If the user says no, stop and explain that Gofer stage/helper work depends on the repo-owned scaffold.
-
-
-# Gofer Stakeholder Communications
-
-## EAI Platform Session Preflight
-
-Before any Gofer stage/helper command does pipeline work:
-
-1. Treat durable delivery as EAI Platform delivery by default, with Azure second
-   and every other stack only by explicit exception.
-2. Run `eai whoami` and confirm the EAI CLI is installed, the user is logged in,
-   and an active workspace is visible.
-3. If `eai` is missing, `eai whoami` fails, the token is expired, or no active
-   workspace is available, stop and run `/gofer:eai-first-run` or ask the user to
-   approve login/setup before continuing.
-4. For EAI app delivery, do not continue into research, specification, planning,
-   tasks, implementation, or validation until
-   `.specify/specs/{feature}/eai-preflight.md` records login, workspace, template,
-   app-readiness, and next-action evidence.
-5. Do not write tokens, secrets, private workspace IDs, Entra/CIAM authority tenant IDs, or local `.env` values into
-   Gofer artifacts; record only product-safe readiness status and evidence.
-
-## Token And Cost Policy
-<!-- gofer:token-cost-policy:start -->
-
-Before spawning agents, calling tools, or loading large files:
-
-1. Treat `.specify/memory/gofer-model-policy.yaml` as the repo-owned source of truth for simple, medium, hard, and arbiter model routing. If it is missing, run `/gofer:bootstrap-workspace` before continuing.
-2. Use the cheapest capable model first.
-   - Claude: Haiku for scouting/extraction; Sonnet for normal implementation, synthesis, validation, and security; Opus for high-risk arbitration or release-critical failures.
-   - Codex/OpenAI: GPT mini for simple coding; GPT nano only for locate/classify/summarize/mechanical work; GPT-5.3-Codex or flagship GPT for tool-heavy coding, architecture, and release-critical validation.
-   - Gemini: Flash-Lite for cheap large-context scan/summarize; Flash for default research synthesis; Pro for large-context architecture or high-risk arbitration.
-   - Copilot: prefer Auto for simple and default work; ask the user before choosing a paid/high-tier picker model for hard security, architecture, or release gates.
-3. Keep raw tool output out of the main conversation context. Save stable findings to `.specify/specs/{feature}/context-bundle.md`, then work from summaries.
-4. Use provider prompt/context caching only for stable, non-secret prefixes: Gofer scaffold, AGENTS/CLAUDE/Copilot instructions, constitution, repo map, stage contracts, and validation rubric.
-5. Before continuing after large research, planning, implementation, or validation bursts, checkpoint the durable artifacts and compact/clear/resume context when the host supports it.
-6. Escalate model tier only when a cheaper pass is low-confidence, contradictory, security-sensitive, or blocking release quality.
-<!-- gofer:token-cost-policy:end -->
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Prerequisites
-
-This command expects in `.specify/specs/{feature}/`:
-
-- `validation-report.md` — Feature validated (PASS) from #6_gofer_validate
-- `problem-brief.md` — Original business problem (from #0a_problem_validation)
-- `spec.md` — Feature specification (from #2_gofer_specify)
-- `spec-summary.md` — Executive summary (from #2_gofer_specify)
-- `assumptions.md` — Tracked assumptions
-- `working-backwards-prfaq.md` — Running product release PR/FAQ updated by stages 0-6
-- `business-owner-summary.md` — Business Owner summary updated by stages 1, 2, 5, and 6
-- `cto-architecture-summary.md` — CTO/Architecture summary updated by stages 3, 5, and 6
-- `ciso-security-summary.md` — CISO/Risk summary updated by #6_gofer_validate
-- `stakeholder-review-index.md` — Current stakeholder review status and approve/revise/defer asks
-
-If `validation-report.md` doesn't exist or shows FAIL, do NOT generate comms.
-Instead, inform the user that validation must pass first.
-
----
-
-## Outline
-
-1. Context health check
-2. Load all feature context
-3. Spawn comms-writer agent
-4. Spawn business-metrics-analyzer agent
-5. Generate stakeholder communications package
-6. Generate business metrics dashboard
-7. Final assumption review
-8. Completion summary
-
----
-
-## Step 0: Context Health Check
-
-```bash
-.specify/scripts/bash/check-context-health.sh
-```
-
-- If **< 50%**: Proceed normally
-- If **50-70%**: Use sub-agents heavily
-- If **> 70%**: Run `#7_gofer_save` first
-
----
-
-## Step 1: Load Feature Context
-
-1. **Run setup script**:
-
-   ```bash
-   .specify/scripts/bash/check-prerequisites.sh --json --require-tasks
-   ```
-
-   Parse JSON for FEATURE_DIR
-
-2. **Load all business artifacts**:
-   - `working-backwards-prfaq.md` — Running product release PR/FAQ and internal FAQ
-   - `stakeholder-review-index.md` — Review status and required approvals
-   - `business-owner-summary.md` — Business scenario, process, value, assumptions
-   - `cto-architecture-summary.md` — Architecture, EAI Platform/Azure fit, auth/workspace/data/contracts
-   - `ciso-security-summary.md` — Security posture, controls, residual risk, validation evidence
-   - `problem-brief.md` — Original problem and business case
-   - `discovery.md` — Business discovery context
-   - `spec-summary.md` — Executive summary
-   - `assumptions.md` — Assumption register
-   - `validation-report.md` — Quality verification results
-   - `tasks.md` — Implementation status
-
-3. **Verify validation passed**:
-   - Check `validation-report.md` for `status: PASS`
-   - If FAIL: "Validation must pass before generating communications. Current
-     score: [N]/110. Run #6_gofer_validate first."
-
----
-
-## Step 2: Spawn Parallel Agents
-
-Launch both agents **in parallel**:
-
-### Agent 1: Communications Writer
-
-```
-Task: subagent_type="comms-writer", model="haiku"
-Prompt: "Generate stakeholder communications for feature [FEATURE_NAME].
-
-Feature directory: {FEATURE_DIR}
-
-Read and use:
-- working-backwards-prfaq.md for the product-release story and FAQ
-- stakeholder-review-index.md for review status and approval asks
-- business-owner-summary.md for business scenario, process, value, and assumptions
-- cto-architecture-summary.md for architecture, EAI Platform/Azure fit, auth, tenancy, data, and contracts
-- ciso-security-summary.md for controls, residual risk, security evidence, and launch gates
-- problem-brief.md for original problem context
-- discovery.md for business discovery findings
-- spec.md for what was specified
-- spec-summary.md for business summary
-- validation-report.md for quality status
-- assumptions.md for tracked assumptions
-
-Generate:
-1. Executive summary (3 sentences)
-2. Non-technical release notes
-3. 5-minute demo script with talking points
-4. Change management brief with rollout plan
-5. Success metrics with baseline and targets
-6. Communication timeline
-
-Return structured report (<2000 tokens)."
-```
-
-### Agent 2: Business Metrics Analyzer
-
-```
-Task: subagent_type="business-metrics-analyzer", model="haiku"
-Prompt: "Analyze pipeline metrics for business reporting.
-
-Feature directory: {FEATURE_DIR}
-Logs directory: .specify/logs/
-
-Read pipeline logs and feature artifacts to produce:
-1. Feature velocity (delivery time for this feature)
-2. Stage duration breakdown
-3. Quality metrics (validation score, iterations)
-4. Cost analysis (token usage)
-5. Portfolio status (active top-level features in .specify/specs/, excluding `_archived/`)
-6. Scope health indicators
-
-Return structured report (<2000 tokens)."
-```
-
-**Run both agents in parallel.**
-
----
-
-## Step 3: Generate Stakeholder Communications
-
-Write to `{FEATURE_DIR}/stakeholder-comms.md` using the template at
-`.specify/templates/stakeholder-comms-template.md`.
-
-Populate with comms-writer agent findings and the running PR/FAQ/persona
-summaries. Ensure:
-
-- **All language is non-technical** — no jargon, no acronyms without explanation
-- **Impact is quantified** — use numbers from problem-brief.md
-- **Demo script is actionable** — someone could run the demo from this document
-- **Change management is realistic** — phased rollout with success criteria
-- **Metrics are tied to problem** — connect back to original business case
-- **The PR/FAQ is preserved** — include a "Product Release PR/FAQ" section or
-  direct links to `working-backwards-prfaq.md` and its stage snapshots
-- **Persona summaries are visible** — include links and decision status for
-  `business-owner-summary.md`, `cto-architecture-summary.md`, and
-  `ciso-security-summary.md`
-
----
-
-## Step 4: Generate Business Metrics Dashboard
-
-Write to `{FEATURE_DIR}/business-metrics.md` using the template at
-`.specify/templates/business-metrics-template.md`.
-
-Populate with business-metrics-analyzer agent findings.
-
----
-
-## Step 5: Final Assumption Review
-
-Spawn the assumption-tracker agent to do a final review:
-
-```
-Task: subagent_type="assumption-tracker", model="haiku"
-Prompt: "Final assumption review for feature [FEATURE_NAME].
-
-Feature directory: {FEATURE_DIR}
-
-Read assumptions.md and cross-reference against:
-- validation-report.md (did implementation reveal any disproven assumptions?)
-- tasks.md (any tasks that changed because of assumption issues?)
-
-Update assumption statuses based on implementation evidence.
-Flag any assumptions that remain UNVALIDATED and could affect launch.
-
-Return structured report (<2000 tokens)."
-```
-
-### Update Assumptions
-
-Based on agent findings, update `{FEATURE_DIR}/assumptions.md`:
-
-- Mark assumptions validated by implementation as `VALIDATED`
-- Mark assumptions disproven during development as `DISPROVEN`
-- Flag remaining `UNVALIDATED` assumptions with recommended verification actions
-
----
-
-## Step 6: Generate Scope Creep Report (If problem-brief exists)
-
-If `{FEATURE_DIR}/problem-brief.md` exists, run scope creep detection:
-
-```
-Task: subagent_type="scope-creep-detector", model="haiku"
-Prompt: "Analyze scope creep for feature [FEATURE_NAME].
-
-Feature directory: {FEATURE_DIR}
-
-Compare the final implementation (tasks.md, spec.md) against the original
-problem brief (problem-brief.md). Calculate scope creep score.
-
-Return structured report (<2000 tokens)."
-```
-
-If scope creep score > 25%, include a "Scope Evolution" section in the
-stakeholder communications explaining what changed and why.
-
----
-
-## Step 7: Completion Summary
-
-```
-════════════════════════════════════════════════════════════════
-  STAKEHOLDER COMMUNICATIONS COMPLETE: [Feature Name]
-════════════════════════════════════════════════════════════════
-
-  Deliverables:
-  - {FEATURE_DIR}/working-backwards-prfaq.md
-  - {FEATURE_DIR}/business-owner-summary.md
-  - {FEATURE_DIR}/cto-architecture-summary.md
-  - {FEATURE_DIR}/ciso-security-summary.md
-  - {FEATURE_DIR}/stakeholder-review-index.md
-  - {FEATURE_DIR}/stakeholder-comms.md
-  - {FEATURE_DIR}/business-metrics.md
-  - {FEATURE_DIR}/assumptions.md (updated)
-
-  Package includes:
-  - Product Release PR/FAQ
-  - Executive Summary
-  - Business Owner Summary
-  - CTO Architecture Summary
-  - CISO Security Summary
-  - Release Notes (non-technical)
-  - Demo Script (5-minute walkthrough)
-  - Change Management Brief
-  - Success Metrics & KPIs
-  - Communication Timeline
-  - Business Metrics Dashboard
-  - Assumption Status Report
-
-  Scope Creep Score: [N]% ([Healthy/Warning/Alert])
-  Assumptions: [N] validated, [N] unvalidated, [N] disproven
-
-════════════════════════════════════════════════════════════════
-  FEATURE PIPELINE COMPLETE!
-
-  Full Pipeline Summary:
-  0a. #0a_problem_validation  ✓ (Problem validated)
-  1.  #1_gofer_research        ✓ (Codebase + market research)
-  2.  #2_gofer_specify         ✓ (Spec + business summary)
-  3.  #3_gofer_plan            ✓ (Technical architecture)
-  4.  #4_gofer_tasks           ✓ (Task breakdown)
-  5.  #5_gofer_implement       ✓ (Implementation)
-  6.  #6_gofer_validate        ✓ (Quality: [score]/110)
-  7a. #7a_stakeholder_comms    ✓ (Communications package)
-
-  The feature is ready for stakeholder review and deployment.
-════════════════════════════════════════════════════════════════
-```
-
----
-
-## Marp Presentation Deck (Opt-In; EnterpriseAI Recommended)
-
-Marp deck generation is opt-in for the standard Gofer workflow and is
-recommended only for `workflowProfile=enterpriseai`, where stakeholders usually
-need a simple walkthrough. When enabled, generate the general stakeholder deck
-and, for larger changes, the persona deck pack. Skip decks only for small
-docs-only or purely mechanical changes where a short Markdown summary is clearer.
-Release Notes and the Demo Script (5-minute walkthrough) remain core
-deliverables as `release-notes.md` and `demo-script.md`.
-
-When a deck is generated, write `{FEATURE_DIR}/presentation.marp.md`. The file
-MUST use Marp frontmatter and the canonical stakeholder slide deck structure:
-
-```markdown
----
-marp: true
-theme: default
-paginate: true
----
-
-# Problem Statement
-
-{{problem-statement}}
-
----
-
-# EnterpriseAI Solution Overview
-
-{{enterpriseai-fit}}
-
----
-
-# Architecture Diagram Reference
-
-See `plan.md` → architecture section.
-
----
-
-# Demo Script Summary
-
-See Release Notes and the Demo Script (5-minute walkthrough) above.
-
----
-
-# Success Metrics
-
-{{success-metrics}}
-```
-
-Every section title above (`Problem Statement`,
-`EnterpriseAI Solution Overview`, `Architecture Diagram Reference`,
-`Demo Script Summary`, `Success Metrics`) is mandatory in both the generated
-`presentation.marp.md` and the corresponding
-`.specify/templates/stakeholder-comms-template.md`.
-
-### Persona Marp Deck Pack
-
-Generate these additional decks under `{FEATURE_DIR}/presentations/`:
-
-| Deck | Decision-Rights Audience | Required Focus |
-| ---- | ------------------------ | -------------- |
-| `executive.marp.md` | Executive committee | Strategic value, funding gate, risk appetite |
-| `business.marp.md` | Business owner | User journey, operational value, adoption |
-| `internal-delivery.marp.md` | Delivery lead | Dependency plan, red/green loop, delivery risks |
-| `enterprise-architecture.marp.md` | Enterprise architecture | Platform fit, context bundle, contract pack, reuse decisions |
-| `ciso.marp.md` | CISO | Identity, workspace boundary, controls, residual risk |
-| `data-architecture.marp.md` | Data architecture | Object types, lineage, quality, governance |
-| `cio.marp.md` | CIO | Platform strategy, operating model, reuse roadmap |
-| `cfo.marp.md` | CFO | Investment case, benefit tracking, cost risk |
-| `coo.marp.md` | COO | Process change, rollout readiness, support model |
-| `risk-compliance.marp.md` | Risk/compliance | Obligations, evidence, exceptions, audit trail |
-
-Every persona deck MUST include:
-
-- Executive Summary.
-- Decision Focus.
-- Problem Statement.
-- EnterpriseAI Solution Overview.
-- AI-Augmented 4-Step Journey for app delivery, or the non-app classification
-  rationale when no app is being built.
-- Architecture Diagram Reference with a Mermaid diagram.
-- Context Bundle.
-- Contract Pack.
-- Reuse-Before-Create.
-- Audit History.
-- Red/Green Validation Loop.
-- Demo Script Summary.
-- Success Metrics.
-- Persona-specific value/risk table and controls table.
-
----
-
-## Step 7.5: Assemble Stakeholder Visual Pack
-
-After all comms artifacts are generated, compose the stakeholder visual pack
-from `{FEATURE_DIR}/visuals/` into a single `stakeholder-pack.md` file. This
-runs in deterministic order (impact-canvas → C4 → value-stream → capability
-heatmap → bounded-context → ERD → risk-heatmap → ROI projection) and skips
-artifacts that were not generated (FR-028, NFR-011, T138).
-
-```bash
-node .specify/scripts/node/lib/assemble-stakeholder-pack.mjs $FEATURE_DIR
-```
-
-The assembler writes `{FEATURE_DIR}/stakeholder-pack.md` and prints which
-artifacts were included vs. missing so the operator can re-run the relevant
-visual generators if needed.
-
-Before presenting the pack, review the included visuals against the visual
-explanation quality gate used by `#6_gofer_validate`:
-
-- Each visual answers one stakeholder question and is simple enough to read
-  without external docs.
-- Each visual has a plain-language preamble, audience, source inputs, and
-  requirement/plan/code/test/EAI evidence links.
-- Each Mermaid/D2/Structurizr-style diagram renders or includes a markdown/text
-  fallback; each UI picture has screenshot, Storybook/component, Playwright, or
-  equivalent render proof.
-- `presentation.marp.md` should exist for substantive stakeholder-facing
-  changes unless the change is small, docs-only, or better explained by a short
-  Markdown summary. If skipped, record the reason in `stakeholder-comms.md`.
-- Every human-facing document starts with a three-to-five-bullet executive
-  summary that explains the decision, value, risk, evidence, and next ask in
-  simple language.
-- Any stale, crowded, private-data-bearing, or untraceable visual is called out
-  in `stakeholder-review-index.md` as `revise visuals <artifact>`.
-
----
-
-## Step 8: Observability Logging
-
-```bash
-.specify/scripts/bash/log-stage.sh 7a_stakeholder_comms --complete --tokens [N] --compactions [N]
-```
-
----
-
-## Important Notes
-
-- **Every output must be copy-pasteable** — consultants share these as-is
-- **No technical jargon** — write for business executives
-- **Connect to business case** — always reference problem-brief.md impact
-  metrics
-- **Be honest about limitations** — known issues build trust
-- **Include timelines** — consultants need to plan around dates
-- **Quantify everything** — numbers > adjectives
-- **Demo script must work** — test it mentally before writing