agile-01: Complete GitHub agile hierarchy (Epic → Feature → User Story)

[djm81]

Change Proposal: agile-01-feature-hierarchy

Status: Active
Priority: Medium
Parent Epic: #194 (Architecture + Marketplace)

Purpose

Complete the GitHub agile hierarchy from two levels (Epic → User Story) to three levels
(Epic → Feature → User Story) so the project board supports coherent sprint-planning
groupings below the Epic level.

Problem

The repo has 12 Epics and ~79 User Story (change-proposal) issues but zero Feature-tier
issues. Sprint planners cannot see which cluster of User Stories delivers a coherent
user-facing or architectural slice of value. There is no natural grouping unit for
mid-level roadmap planning, velocity tracking per theme, or cross-team scoping conversations.

Additionally, Epics #256, #257, and #258 (created as part of the 2026-02-15 architecture
integration plan) are not recorded in openspec/CHANGE_ORDER.md's "Parent issues (Epics)"
section.

Proposed Change

1. Create 25 Feature issues (F1–F25), each linked to its parent Epic
2. Set parent (User Story → Feature) for all ~79 change-proposal issues
3. Update openspec/CHANGE_ORDER.md to add Epics [Epic] Architecture Layer Integration (Requirements to AI) #256, [Epic] AI IDE Integration #257, [Epic] Integration Governance and Dogfooding #258
4. Close issue [Change] Ceremony Cockpit (UX layer for findability) — Δ3 #185 (ceremony-cockpit-01, confirmed archived 2026-02-18)

Scope

No source code changes. GitHub operations + one CHANGE_ORDER.md update only.

Feature Mapping (F1–F25)

Feature	Title	Epic	Child Stories
F1	Modular CLI Foundation	#194	#193, #199, #203, #206, #207
F2	Module Security & Schema Extensions	#194	#208, #213
F3	Marketplace Module Distribution	#194	#214, #215, #327, #328, #329
F4	Module Migration & CLI Reorganization	#194	#315, #316, #317, #330, #338, #339
F5	Developer Workflow & CI Pipeline	#194	#267, #260, #276
F6	Documentation & Discrepancy Remediation	#194	#291, #348
F7	Backlog Core Commands	#186	#116, #155, #158, #166, #173, #295, #298, #310, #337
F8	Backlog Authentication	#186	#340
F9	Scrum Workflows	#186	#168, #175, #220, nold-ai/specfact-cli-modules#152, nold-ai/specfact-cli-modules#160, nold-ai/specfact-cli-modules#153
F10	Kanban Flow Metrics	#186	nold-ai/specfact-cli-modules#155
F11	SAFe & PI Planning	#186	nold-ai/specfact-cli-modules#154, nold-ai/specfact-cli-modules#156
F12	Policy Engine & Enforcement Modes	#187	#176, nold-ai/specfact-cli-modules#158
F13	Ceremony Command Layer	#189	#185, nold-ai/specfact-cli-modules#159
F14	Deep Codebase Validation	#190	#163
F15	Configuration Profiles	#256	#237, #249, #250
F16	Requirements Layer	#256	#238, #239, #244
F17	Solution Architecture Layer	#256	#240
F18	Full-Chain Validation & Traceability	#256	#241, #242
F19	Sync Engine	#256	nold-ai/specfact-cli-modules#157
F20	Governance, Policy Packs & Evidence	#256	nold-ai/specfact-cli-modules#158, #247, #248
F21	OpenSpec Bridge Integration	#256	#350
F22	Agent Skills & Instruction Files	#257	#251, #253, #349
F23	MCP Server	#257	#252
F24	End-to-End Integration Proof	#258	#254, #255
F25	CLI Behavior Validation Suite	#285	#279, #280, #281, #282, #283, #284

OpenSpec Change Folder

openspec/changes/agile-01-feature-hierarchy

[djm81]

Validated on 2026-04-08: the Epic -> Feature -> User Story hierarchy is already in place in GitHub, CHANGE_ORDER was reconciled, and OpenSpec change agile-01-feature-hierarchy has been archived as 2026-04-08-agile-01-feature-hierarchy.