docs: promote reusable AeroSim channel lessons

This commit is contained in:
jarvis-at-skic committed 2026-10-20 18:42:45 +00:00
1 parent 602b1a0afd
commit 5a09d92abd
5 files changed
+109 -58

No files matched your search

+25 -12
View File
@@ -1,7 +1,7 @@
---
name: corp-v1-channel-scope
description: "Use when operating or synchronizing a Corp v1 project's Scope channel. Owns Roadmap, Epics, Features, and Ideas; correlates all seven same-project channels; proactively improves evidence-based product scope; and records human approval before work enters Architecture solution design."
version: 1.7.0
description: "Use when operating or synchronizing a Corp v1 project's Scope channel. Owns Roadmap, Epics, Features, and Ideas; correlates all eight same-project channels; proactively improves evidence-based product scope; and records human approval before work enters Architecture solution design."
version: 1.8.0
author: Hermes Agent
license: MIT
metadata:
@@ -18,7 +18,7 @@ metadata:
Whenever a response mentions a Hermes Kanban board, initiative, card, or task, it must include a direct dashboard link in the form `[descriptive board label](<dashboard-public-url>/kanban?board=<board-slug>)`. Resolve the dashboard public URL and exact board slug before reporting; never provide only a board name, slug, card count, “visible cards,” or “available in the dashboard.” If no task-specific deep link exists, link the board and include the exact task ID or title in the same statement. Project-adopted skills must replace this generic form with their verified project board URL.
This skill owns product discovery and durable scope for a Corp v1 project's `scope` channel. It monitors the seven same-project channels—`general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, and `releases`—and maintains the project documentation's top-level **Scope** area.
This skill owns product discovery and durable scope for a Corp v1 project's `scope` channel. It monitors the eight same-project channels—`general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, `uat`, and `releases`—and maintains the project documentation's top-level **Scope** area.
Scope owns Overview, Roadmap, Epics, Features, canonical Task records/reader pages, Ideas, and Questions. General coordinates overall project awareness but does not duplicate Scope records. Architecture performs solution work only for Features explicitly approved for solution by a human team member and remains semantic owner of requirement/task derivation, dependencies, and readiness. Hermes participates proactively by proposing and refining useful scope, but never approves its own proposals.
@@ -53,6 +53,8 @@ Do not use it to design architecture, approve solution entry, approve implementa
## Approved Information Boundary
Follow the eight-channel topology in `corp-v1-main`, approved by Board message `1552966246591365123`; include UAT between Delivery and Releases. Verify mapped IDs and effective access before reading.
Inspect only:
```text
@@ -62,10 +64,11 @@ corp-v1-<code>-architecture
corp-v1-<code>-ui-ux
corp-v1-<code>-kanban
corp-v1-<code>-delivery
corp-v1-<code>-uat
corp-v1-<code>-releases
```
Read enough Scope history to avoid duplicates and only relevant new activity from the other six channels. Never inspect or correlate another project's channels.
Read enough Scope history to avoid duplicates and only relevant new activity from the other seven channels. Never inspect or correlate another project's channels.
## Human Approval Gate
@@ -113,9 +116,11 @@ Maintain a dedicated **Overview** page at canonical route `/scope/overview/` as
Generate the matrix from the same validated canonical data and status selector used by Roadmap and Board views. Include every item, including `DONE` and `CANCELLED`, with at least:
```text
ID | type | title | direct parent/resulting scope | delivery status | EXACT/DERIVED | blocked flag/reason | owner | approval gates | required children | dependencies | release/deployment evidence | last evidenced transition | canonical record link
ID | type | title | direct parent/resulting scope | delivery status | Status basis | blocked flag/reason | owner | approval gates | required children | dependencies | release/deployment evidence | last evidenced transition | canonical record link
```
Keep `status_source: EXACT`/`DERIVED` internal; render **Status basis** as `Exact item evidence`/`Required-child roll-up`, separate from the unchanged canonical status.
Provide type/status totals and filters. Render exactly one semantic matrix table: it initially contains every governed record, and search/type/status controls narrow that same table. Do not add a second “complete unfiltered” disclosure or duplicate table. Keep the current table usable for print, accessibility, and no-JavaScript output. Sort deterministically by hierarchy and stable ID. Link every row to its canonical record and every relationship to the resolved target record.
Fail validation when any canonical item is absent or duplicated; a required relationship is dangling, one-sided, or double-counted; a status is invalid for the item type; `status_source` is missing or wrong; a derived status disagrees with the unified roll-up algorithm; a blocked item lacks a reason; or a transition/evidence link is not durable. The page must expose stale or contradictory states rather than silently filtering them out.
@@ -265,14 +270,20 @@ Acceptance requires canonical-YAML validation, graph/table parity where a semant
Every Scope iteration must add or materially improve at least one evidence-based scope artifact when a safe path exists: a grounded Idea, Epic, or Feature; clearer value or acceptance outcomes; dependency/risk evidence; deduplication; Roadmap reconciliation; cross-links; or a concrete unanswered product question. Never create filler to satisfy cadence.
Use evidence from all seven same-project channels. Delivery and release outcomes may expose new Ideas or required scope corrections; Architecture may expose infeasible assumptions; Kanban may expose flow or dependency problems. Preserve authority boundaries while incorporating that evidence.
Use evidence from all eight same-project channels. Delivery and release outcomes may expose new Ideas or required scope corrections; Architecture may expose infeasible assumptions; Kanban may expose flow or dependency problems. Preserve authority boundaries while incorporating that evidence.
### Acceptance-gap discovery
When verified implementation or deployment precedes item-specific approval, record an acceptance gap, not retroactive approval. Attribute channel reports as reports unless independently verified. For each canonical outcome classify only `demonstrated`, `contradicted`, or `not demonstrated by the cited evidence`; missing evidence does not prove an outcome was untested. Bind coverage to the immutable Scope revision defining the outcome set and the distinct tested application revision; require one row per outcome and all capture fields before calling coverage complete. Re-evaluate completeness when Scope changes. Follow the packet contract in [data-backed Scope integrity](references/data-backed-scope-integrity.md#reproducible-acceptance-evidence-packet-consistency).
Keep newest published source and actually deployed/tested source distinct. Never transfer runtime observations to a newer unobserved revision. Discovery, capture completion, healthy deployment and documentation merge do not grant acceptance, admission, release approval or lifecycle transitions.
## Handoffs
- **Scope → Architecture:** only human-approved Features with stable ID, parent Epic, value, scope, acceptance outcomes, dependencies, risks, and approval evidence.
- **Architecture → Scope:** feasibility constraints, requirement implications, dependencies, and proposed scope clarifications; Architecture does not silently rewrite product scope.
- **Scope → Kanban:** stable Idea/Epic/Feature identities, required-child relationships, approval gates, and unified delivery status for Board/Focus reconciliation.
- **Delivery/Releases → Scope:** verified outcomes, regressions, user feedback, and follow-up opportunities that may alter the Roadmap or create Ideas.
- **Delivery/UAT/Releases → Scope:** verified outcomes, regressions, user feedback, and follow-up opportunities that may alter the Roadmap or create Ideas.
- **Scope → General:** concise overall implications, decisions requiring visibility, owners, and cross-channel blockers.
## UI/UX Coordination
@@ -281,15 +292,15 @@ Scope supplies UI/UX with stable Feature identity, user problems, value, accepta
## Synchronization Workflow
1. Confirm the exact project code and seven approved channel IDs.
2. Read new activity from the other six channels and enough Scope history to avoid duplication.
1. Confirm the exact project code and eight approved channel IDs.
2. Read new activity from the other seven channels and enough Scope history to avoid duplication.
3. Separate verified facts, human decisions, proposals, forecasts, and unresolved questions.
4. Inspect Overview, Roadmap, Ideas, the exact Epics → Epic → Questions → Question and Epics → Epic → Features → Feature → Tasks hierarchies, every separate Question and Task reader page, links, IDs, unified delivery statuses, required-child roll-ups, and approval evidence.
5. Reconcile architecture feasibility, Kanban flow, delivery progress, and release outcomes against scope.
6. Add or materially improve at least one useful evidence-based artifact, or document the exact evidence/approval blocker.
7. Load `documentation-docusaurus` and the project CI/CD skill. Run only fast, dependency-free local preflight checks such as schema/parity scripts, targeted tests already available, `git diff --check`, and secret scanning. Do not spend the working session installing dependencies or repeatedly running the full documentation build locally when PR-triggered Gitea Actions can provide the authoritative environment.
8. Push the smallest coherent reviewable branch early and open or refresh its PR. The PR workflow must install dependencies and run the complete canonical-data validation, tests, typecheck, strict production build, and built-site assertions without publishing. Wait for the run attached to the exact pushed SHA; inspect failed job steps and logs, fix only evidenced defects, push, and repeat until that exact head is green.
9. Review the exact CI-green head, merge through the repository workflow, then require default-head CI/publication success and deployed remote readback before reporting completion. Never treat a local build, a stale run, or CI for another SHA as acceptance evidence.
8. Satisfy any required pre-publication review before push; the early-PR workflow does not waive the independent review required for data-backed migrations. If a required pre-publication channel record cannot be delivered in this execution context, keep the candidate local and report that precise publication block. Push the smallest coherent reviewable branch early and open or refresh its PR. The PR workflow must install dependencies and run the complete canonical-data validation, tests, typecheck, strict production build, and built-site assertions without publishing. Wait for the run attached to the exact pushed SHA; inspect failed job steps and logs, fix only evidenced defects, push, and repeat until that exact head is green.
9. Review the complete candidate diff against its verified base, including older committed changes and untracked candidate files. Keep a claim ledger for dynamic source, PR, CI and runtime assertions; evidence-through times must cover every cited source within their stated boundary. Fix actual artifact defects, but correct missing ledger evidence without churning already-correct prose. Preserve the required review type: self-review is not a substitute for independent review. Merge only with applicable authorization, then require default-head CI/publication success and deployed page-body readback. A redirect to an identity-provider login page with HTTP 200 is not content verification; report that boundary rather than claiming publication verified. Never transfer a review to a changed base merely because the patch hash is unchanged.
10. Post a concise Scope update. When verification is successful and the human did not ask for delivery evidence, report only the substantive changes and the reader-facing documentation link; omit routine test, build, CI, audit, PR, run, commit, and SHA details. Internal validation and immutable evidence remain mandatory. Include technical evidence only when requested or when a failure, blocker, or unresolved publication state makes it actionable. Handoff packets retain their explicit evidence contract. Prefer the most specific verified documentation route, and include the portal landing page when several pages changed. If default-head publication or page-body verification is still pending, say so instead of presenting the route as published, then provide the documentation link in the completion follow-up. Stay silent when no substantive result exists.
## Authority and Escalation
@@ -327,6 +338,8 @@ When a human asks whether an Epic contains all Features required for its outcome
Refine experiential requests into observable loops: entry/start, continuous user control, meaningful state change, visible feedback, outcome/failure, and replay/recovery. Keep feasibility research separate from solution selection. For Epic-wide constraints, create one canonical cross-cutting question, link it reciprocally to every affected Feature, validate both directions, and search for stale count/range assertions. Use [references/roadmap-multidimensional-state.md](references/roadmap-multidimensional-state.md) and [references/react-flow-governed-state.md](references/react-flow-governed-state.md) when the project uses data-backed readers or graphs.
Source comparison and exclusions: [AeroSim lessons review](references/aerosim-lessons-review.md).
## Common Pitfalls
1. Treating General as the authoritative owner of Scope records.
@@ -355,7 +368,7 @@ Refine experiential requests into observable loops: entry/start, continuous user
## Verification Checklist
- [ ] Only the seven same-project channels were inspected.
- [ ] Only the eight same-project channels were inspected.
- [ ] Scope appears immediately before Architecture with its own sidebar.
- [ ] Sidebar order is Overview, Roadmap, Ideas with child pages, then Epics; every Epic contains explicit Questions and Features groups.
- [ ] Ways of Working starts with a separate Scope page explaining the ticket hierarchy and governed statuses.