📖 [Docs]: Issue planning, types, and relationships are defined#94
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR expands the “Issues → Process” documentation to define how issues evolve through the workflow, how planning detail is added progressively, and how GitHub-native relationships define containment and execution order—while simplifying the “Format” page down to universal rules.
Changes:
- Added new Process pages for lifecycle, planning, and relationship guidance.
- Refactored “Issue Format” to only include rules shared by all issue types and defer type-specific detail elsewhere.
- Updated site navigation and the Process index to include the new pages.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| src/zensical.toml | Adds the new Process pages to the Zensical nav tree. |
| src/docs/Ways-of-Working/Issues/Process/Relationships.md | Defines native containment/dependency semantics and rejects manual relationship duplication. |
| src/docs/Ways-of-Working/Issues/Process/Planning.md | Introduces “planning altitudes” and progressive Why/How/What decomposition guidance. |
| src/docs/Ways-of-Working/Issues/Process/Lifecycle.md | Maps how issues’ bodies/types/relationships evolve across workflow phases. |
| src/docs/Ways-of-Working/Issues/Process/index.md | Updates the Process index entries to include the new pages. |
| src/docs/Ways-of-Working/Issues/Process/Format.md | Replaces the prior detailed format spec with universal rules and cross-links to the new guidance. |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 12 out of 12 changed files in this pull request and generated 4 comments.
Comments suppressed due to low confidence (1)
src/docs/Ways-of-Working/Issues/Types/PBI.md:25
- “nested-PBI” is hyphenated here but elsewhere the docs use “nested PBI(s)”. Keeping it unhyphenated avoids inconsistent terminology.
- Explain the decomposition into Task, Bug, or nested-PBI children.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
|
Generated-index note: |
Issue guidance now explains how bodies, types, readiness, and native relationships evolve from capture through operation while keeping the Workflow page authoritative for phase definitions.
New: Issue lifecycle, planning, and relationships
The Process section now maps issue evolution onto the shared workflow, explains progressive Why/How/What decomposition, and establishes GitHub sub-issues and dependency edges as the authoritative containment and execution-order model. Ready siblings without dependency edges can proceed in parallel.
New: Native issue type guidance
Dedicated Epic, PBI, Task, and Bug pages now define the body detail, readiness, planning altitude, and completion rules for each native type. The shared hierarchy page focuses on taxonomy, routing, containment, and promotion or demotion.
Changed: Universal issue format
Issue Format now contains only rules shared by every native type and routes readers to the type-specific guidance. Manual relationship fields, copied child lists, and list-order sequencing are explicitly rejected.
Technical details
Issues/Process/.Relevant issues (or links)