docs: promote reusable AeroSim channel lessons
Validate skill / validate (push) Successful in 11s
Validate skill / validate (pull_request) Successful in 10s

This commit is contained in:
jarvis-at-skic committed 2026-10-20 18:42:37 +00:00
1 parent a599b11944
commit 0f1b949ff0
10 files changed
+116 -20

No files matched your search

+11 -8
View File
@@ -1,7 +1,7 @@
---
name: corp-v1-channel-architecture
description: "Use when operating or synchronizing a Corp v1 project's architecture channel. Maintains C4-based architecture documentation, Draw.io diagrams, architecture decisions, and requirements while correlating verified activity across the project's seven channels."
version: 1.9.0
description: "Use when operating or synchronizing a Corp v1 project's architecture channel. Maintains C4-based architecture documentation, Draw.io diagrams, architecture decisions, and requirements while correlating verified activity across the project's eight channels."
version: 1.10.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 the solution phase and architecture coherence for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, and `releases` channels, transforms human-approved Features into requirements and solution artifacts, breaks them into dependency-aware implementation tasks, assigns approved Features to versions, and maintains the Architecture section of the project documentation.
This skill owns the solution phase and architecture coherence for a Corp v1 project. It monitors the project's `general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, `uat`, and `releases` channels, transforms human-approved Features into requirements and solution artifacts, breaks them into dependency-aware implementation tasks, assigns approved Features to versions, and maintains the Architecture section of the project documentation.
The default architecture model is C4. Architecture diagrams must be authored and validated using the global `diagrams-drawio` skill from:
@@ -82,10 +82,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
```
Use mapped-channel history to avoid duplicate work and new relevant activity from the other six channels. Never inspect another project's channels.
Use mapped-channel history to avoid duplicate work and new relevant activity from the other seven channels. Never inspect another project's channels.
## Architecture Documentation Contract
@@ -132,7 +133,7 @@ Documentation and diagrams must reflect approved/current truth. Proposed designs
For each human-approved Feature from canonical Scope:
1. verify its stable ID, parent Epic, scope, value, acceptance outcomes, status, and human approval evidence;
2. set solution status to `In Solution` without changing product approval history;
2. use the canonical repository schema for solution status without changing product approval history; do not invent an intermediate state absent from that schema;
3. derive traceable FRs and NFRs;
4. update C4 views and draft/maintain ADRs as needed;
5. break the Feature into implementation tasks with dependencies and acceptance evidence;
@@ -252,7 +253,7 @@ After human Feature implementation approval, Architecture applies the `READY_FOR
## Proactive Iteration Requirement
Every architecture iteration must add or materially improve a useful project-documentation artifact for an eligible human-approved Feature: FR/NFR traceability, C4/ADR content, task decomposition, dependency mapping, risk analysis, version proposal, or review package. Prefer improving existing artifacts over creating duplicates. If no Feature is approved for solution, document the exact waiting gate or actionable clarification instead of advancing unapproved work.
When eligible work or material drift exists, an architecture iteration must add or materially improve a useful project-documentation artifact for an eligible human-approved Feature: FR/NFR traceability, C4/ADR content, task decomposition, dependency mapping, risk analysis, version proposal, or review package. Prefer improving existing artifacts over creating duplicates. If no Feature is approved for solution, document the exact waiting gate or actionable clarification instead of advancing unapproved work. When that durable gate is already accurate and no material evidence changed, verify and report unchanged status only as needed; do not manufacture an edit to satisfy iteration activity.
## UI/UX Coordination
@@ -264,7 +265,7 @@ Architecture supplies UI/UX with system boundaries, interfaces, data availabilit
2. Inspect documented Epics/Features and verify human `Approved for Solution` evidence before selecting work.
3. Identify changed assumptions, requirements, interfaces, constraints, infrastructure, deployment topology, or runtime behavior.
4. Compare evidence with the required Architecture information architecture, C4 views, ADRs, FR/NFR registries and pages, Scope-hosted task records, dependencies, readiness, and version evidence.
5. Add or materially improve at least one useful solution artifact for an eligible Feature.
5. Apply the Proactive Iteration Requirement: improve eligible artifacts or maintain the exact waiting gate; avoid edits for unchanged evidence.
6. Use `diagrams-drawio` for every diagram change and `documentation-docusaurus` for every documentation, navigation, MDX, plugin, or embedding change.
7. Validate the exact Architecture sidebar, FR/NFR registries and reader pages, absence of Architecture Feature/task navigation, reciprocal Scope traceability, links, Draw.io source embedding, Docusaurus build, and browser rendering; then perform remote readback.
8. Post a concise update with changed artifacts, implications, unresolved decisions, approval gate, and exact evidence.
@@ -299,6 +300,8 @@ Every project adoption must bind this channel to a dedicated local workspace und
## Project-Adoption Architecture Lessons
Apply [references/aerosim-lessons-review.md](references/aerosim-lessons-review.md) for pre-approval intake, scope-to-board coverage, accepted-output evidence, source-of-truth changes and no-churn synchronization. It records pinned sources and exclusions without replacing project tools or approval authority.
Resolve authority from the active project authorization contract at invocation time; broad delegation never replaces exact-item evidence, safety boundaries, or a later narrower owner decision. Use [references/authority-precedence-and-concurrent-evidence.md](references/authority-precedence-and-concurrent-evidence.md).
For cross-channel handoffs, emit a stable verified packet and let the destination re-check its own entry gates. Process each handoff ID once and return incomplete work without fabricating a lifecycle transition. Follow [references/channel-handoff.md](references/channel-handoff.md).
@@ -331,7 +334,7 @@ Use RED-first repository contracts for delegated solution packages and task iden
## Verification Checklist
- [ ] Only the seven same-project channels were inspected.
- [ ] Only the eight same-project channels were inspected.
- [ ] Architecture documentation reflects verified status.
- [ ] C4 scope and level are appropriate.
- [ ] `diagrams-drawio` governed every diagram change.