From 53417c83f36a9577c96111ad6cc0930460fed741 Mon Sep 17 00:00:00 2001 From: Jarvis Jr Hermes Date: Wed, 19 Aug 2026 07:28:05 +0000 Subject: [PATCH] docs(scope): enforce requested sidebar order --- SKILL.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/SKILL.md b/SKILL.md index 132fd48..d385b71 100644 --- a/SKILL.md +++ b/SKILL.md @@ -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 six same-project channels; proactively improves evidence-based product scope; and records human approval before work enters Architecture solution design." -version: 1.3.1 +version: 1.3.2 author: Hermes Agent license: MIT metadata: @@ -62,18 +62,18 @@ Record approver identity, decision evidence, date, resulting status, and conditi ```text Overview Roadmap -Epics - -EP-1 - -FT-1 - -FT-2 - -EP-2 - ... Ideas -IDEA-1 ... Questions Q-0001 ... +Epics + -EP-1 + -FT-1 + -FT-2 + -EP-2 + ... ``` The project documentation's **Ways of Working** area must contain a separate first sidebar item named **Scope** explaining the ticket hierarchy, delivery statuses, exact/derived authority, roll-up, blockers, cancellation, dependencies, gates, and evidence rules. @@ -284,7 +284,7 @@ Requires human approval for: - [ ] Only the six same-project channels were inspected. - [ ] Scope appears immediately before Architecture with its own sidebar. -- [ ] Sidebar order is Overview, Roadmap, Epics with nested Features, Ideas with child pages, then Questions with child pages. +- [ ] Sidebar order is Overview, Roadmap, Ideas with child pages, Questions with child pages, then Epics with nested Features. - [ ] Ways of Working starts with a separate Scope page explaining the ticket hierarchy and governed statuses. - [ ] Ideas and Questions use table-free parent/child pages; no Product Register page exists. - [ ] Roadmap distinguishes verified current state from predicted plans. -- 2.54.0