Repository navigation
Define Epic, PBI, Task, and Bug issue bodies #87
Description
Activity
Scope correction before implementation: Process Task #88 already owns the canonical Format page, so this Task now owns only
Issues/Types/andTypes/Hierarchy.md. The duplicated Format acceptance line was replaced with a Types-only rule. This preserves true parallel execution and avoids a shared-file conflict; #88 still explicitly removes the legacy label wording from Format.Implementation is published in draft PR #93 from commit
26c217a.- Confirmed the branch started exactly at live
origin/main(39411c5) and contains blocker squash3e04c260 - Added dedicated OKF pages for Epic, PBI, Task, and Bug with complete frontmatter
- Updated only the owned Types navigation subsection and generated Types index
- Index and full-link validation pass for this checkpoint
- Hierarchy reduction and complete validation remain in progress
- Confirmed the branch started exactly at live
The owned implementation is complete through commit
c4e9d24and local validation is green.- Reduced Hierarchy to shared taxonomy, routing, native containment/dependencies, and promotion/demotion; detailed bodies now live only on the four type pages
- Preserved the existing inbound
#how-to-express-the-hierarchyanchor without editing any Process or cross-document page Update-DocumentationIndex.ps1update and-Checkpassed- Full
Test-DocumentationLink.ps1passed: all documentation links resolve - Zensical 0.0.50 clean build passed with no issues
- The branch remains limited to
Issues/Types/and the Types subsection ofsrc/zensical.toml; pinned Super-Linter and the other PR jobs are running in CI
All pull request CI jobs are green on PR #93.
- Build passed, including index verification and clean Zensical generation
- Links passed across the full documentation tree
- Lint passed, including Markdown, natural-language, codespell, merge-marker, and security/config validators
- The explicit Copilot review round is now starting
The first explicit Copilot review round found one valid terminology mismatch in
Epic.md.- Replaced "Mission-to-Initiative model" with the linked framework's Mission, OKR, and Initiative terminology
- Published the isolated review fix in commit
6c48e9b - Full-link validation remains green; CI and a fresh Copilot round will run on the new head
The automated review loop has converged on commit
6c48e9b.- Review-fix CI passed Build, Links, and Lint
- The Copilot thread received a reply and is resolved
- A fresh explicit Copilot round completed with
COMMENTED, zero inline comments, and a clean result - Every implementation and validation checklist item is complete
- Live
origin/mainremains39411c5and is fully included in the branch
PR #93 is ready for independent review and squash auto-merge is enabled.
- The pull request remains open and
BLOCKED; it has not merged - Build, Links, and Lint are green on the final head
6c48e9b - The latest explicit Copilot round is clean with zero new inline comments, and all review threads are resolved
- Assignment is
MariusStorhaugand the only label isNoRelease - Auto-merge will wait for the required independent approval before landing
- The pull request remains open and
A valid ambiguity found while reviewing combined PR #94 has been propagated to #87.
- Clarified that Task and Bug do not aggregate implementation work through sub-issues; they still own implementation directly
- Published the isolated Types-only fix in commit
348e58e - Index check, full links, and clean Zensical build remain green
- Final CI and a fresh explicit Copilot round are rerunning on PR 📖 [Docs]: Native issue types now have dedicated guidance #93
The propagated Hierarchy clarification has passed every refreshed gate on head
348e58e.- Final Build, Links, and Lint passed
- A fresh explicit Copilot round completed with
COMMENTED, zero new inline comments, and a clean result - The change remains limited to the Types-owned Hierarchy page
Three additional valid Types grammar findings from combined PR #94 have been propagated to #87 in commit
6d48368.- Pluralized Tasks and Bugs in PBI guidance
- Normalized nested PBI wording and removed inconsistent hyphenation
- Regenerated the Types index from corrected frontmatter
- Index update/check, full links, and clean Zensical build passed; final CI and a fresh Copilot round are rerunning
The propagated Types grammar fixes have passed every refreshed gate on final head
6d48368.- Final Build, Links, and Lint passed
- A fresh explicit Copilot round completed with
COMMENTED, zero new inline comments, and a clean result - PR 📖 [Docs]: Native issue types now have dedicated guidance #93 remains ready with squash auto-merge enabled and awaits independent approval
Live-default closure audit found
origin/mainadvanced tof3aede8through PR #95, which changed only PR description guidance.- Returned PR 📖 [Docs]: Native issue types now have dedicated guidance #93 to draft and cleared auto-merge before refreshing
- Merged live main in commit
ea94f00with the required trailer - Verified the base-relative diff remains limited to the owned Types subtree and Types nav subsection
- Updated the PR body to the new required ending-block format
- Index update/check, full links, and clean Zensical build passed; refreshed CI and explicit Copilot review are running
Delivery has been consolidated into combined PR #94 at the user's direction.
- Verified every file under
Issues/Types/is identical between final PR 📖 [Docs]: Native issue types now have dedicated guidance #93 and PR 📖 [Docs]: Issue planning, types, and relationships are defined #94 - Verified the only
src/zensical.tomldifference is 📖 [Docs]: Issue planning, types, and relationships are defined #94's owned Process navigation entries - Added
Fixes MSXOrg/docs#87to 📖 [Docs]: Issue planning, types, and relationships are defined #94 under the current required PR ending-block format - Closed PR 📖 [Docs]: Native issue types now have dedicated guidance #93 as superseded so one pull request owns the final merge path
- PR 📖 [Docs]: Issue planning, types, and relationships are defined #94 retains the complete Define Epic, PBI, Task, and Bug issue bodies #87 commit/content history and green temporary-stack validation
- Verified every file under
- added a commit that references this issue
on Jul 26, 2026
The native issue types represent different planning altitudes and cannot share one undifferentiated three-section body. Aggregators need outcome and decomposition guidance; delivery leaves need implementation-ready detail.
Request
Add one concise Types page for Epic, PBI, Task, and Bug, and reduce Hierarchy to the shared taxonomy, promotion/demotion, and containment overview.
Acceptance criteria
Technical decisions
Single type slot: Epic, PBI, Task, and Bug use native issue types. Feature describes work kind rather than planning altitude and is retired only after migration.
Leaf delivery: Task and Bug are the only issue types that directly own implementation branches and closing pull requests. Operational Tasks without a repository artifact close through explicit, verified evidence recorded in the issue.
Aggregate delivery: Epic and PBI progress comes from native sub-issues. They close only when children and aggregate acceptance criteria are complete.
File ownership: This Task owns only the Types subtree and
Types/Hierarchy.md. Process Task #88 exclusively ownsProcess/Format.md, including removal of legacy Bug/Feature label wording.Implementation plan
Type pages
Validation