corp-v1-3darch-skills-code-agent/corp-v1-channel-scope-3darch
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: include UI UX in channel coordination

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-25 08:18:07 +00:00
parent d893597905
commit 924ab161df
1 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SKILL.md
+13 -8
View File
@@ -1,7 +1,7 @@
--- ---
name: corp-v1-channel-scope 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 six same-project channels; proactively improves evidence-based product scope; and records human approval before work enters Architecture solution design." 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.5.1 version: 1.5.2
author: Hermes Agent author: Hermes Agent
license: MIT license: MIT
metadata: metadata:
@@ -14,7 +14,7 @@ metadata:
## Overview ## Overview
This skill owns product discovery and durable scope for a Corp v1 project's `scope` channel. It monitors the six same-project channels—`general`, `scope`, `architecture`, `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 seven same-project channels—`general`, `scope`, `architecture`, `ui-ux`, `kanban`, `delivery`, 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. 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.
@@ -44,12 +44,13 @@ Inspect only:
corp-v1-<code>-general corp-v1-<code>-general
corp-v1-<code>-scope corp-v1-<code>-scope
corp-v1-<code>-architecture corp-v1-<code>-architecture
corp-v1-<code>-ui-ux
corp-v1-<code>-kanban corp-v1-<code>-kanban
corp-v1-<code>-delivery corp-v1-<code>-delivery
corp-v1-<code>-releases corp-v1-<code>-releases
``` ```
Read enough Scope history to avoid duplicates and only relevant new activity from the other five channels. Never inspect or correlate another project's channels. 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.
## Human Approval Gate ## Human Approval Gate
@@ -241,7 +242,7 @@ 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. 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 six 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 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.
## Handoffs ## Handoffs
@@ -251,10 +252,14 @@ Use evidence from all six same-project channels. Delivery and release outcomes m
- **Delivery/Releases → Scope:** verified outcomes, regressions, user feedback, and follow-up opportunities that may alter the Roadmap or create Ideas. - **Delivery/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. - **Scope → General:** concise overall implications, decisions requiring visibility, owners, and cross-channel blockers.
## UI/UX Coordination
Scope supplies UI/UX with stable Feature identity, user problems, value, acceptance outcomes, and approval evidence. UI/UX may explore proposals but only an approved design package may become implementation-readiness evidence; Scope remains authoritative for product outcome and disposition.
## Synchronization Workflow ## Synchronization Workflow
1. Confirm the exact project code and six approved channel IDs. 1. Confirm the exact project code and seven approved channel IDs.
2. Read new activity from the other five channels and enough Scope history to avoid duplication. 2. Read new activity from the other six channels and enough Scope history to avoid duplication.
3. Separate verified facts, human decisions, proposals, forecasts, and unresolved questions. 3. Separate verified facts, human decisions, proposals, forecasts, and unresolved questions.
4. Inspect Overview, Roadmap, Ideas, Questions, the exact Epics → Epic → Features → Feature → Tasks hierarchy, every separate Task reader page, links, IDs, unified delivery statuses, required-child roll-ups, and approval evidence. 4. Inspect Overview, Roadmap, Ideas, Questions, the exact Epics → Epic → Features → Feature → Tasks hierarchy, every separate 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. 5. Reconcile architecture feasibility, Kanban flow, delivery progress, and release outcomes against scope.
@@ -306,7 +311,7 @@ Requires human approval for:
## Verification Checklist ## Verification Checklist
- [ ] Only the six same-project channels were inspected. - [ ] Only the seven same-project channels were inspected.
- [ ] Scope appears immediately before Architecture with its own sidebar. - [ ] Scope appears immediately before Architecture with its own sidebar.
- [ ] Sidebar order is Overview, Roadmap, Ideas with child pages, Questions with child pages, then the exact Epics → Epic → Features → Feature → Tasks hierarchy. - [ ] Sidebar order is Overview, Roadmap, Ideas with child pages, Questions with child pages, then the exact Epics → Epic → Features → Feature → Tasks hierarchy.
- [ ] Ways of Working starts with a separate Scope page explaining the ticket hierarchy and governed statuses. - [ ] Ways of Working starts with a separate Scope page explaining the ticket hierarchy and governed statuses.