Skip to content

docs: add planning index consistency review#29

Merged
flyingrobots merged 2 commits intomainfrom
docs/tr-010-planning-index-consistency-review
Mar 30, 2026
Merged

docs: add planning index consistency review#29
flyingrobots merged 2 commits intomainfrom
docs/tr-010-planning-index-consistency-review

Conversation

@flyingrobots
Copy link
Copy Markdown
Member

@flyingrobots flyingrobots commented Mar 30, 2026

Summary

  • land TR-010 with an explicit planning-index consistency review in the workflow doctrine
  • extend the docs checklist with planning-surface alignment checks and triggers
  • close the cycle in backlog/design/archive/legend surfaces and fix archived Truth card links uncovered during the review

Verification

  • npx prettier --check CHANGELOG.md CONTRIBUTING.md WORKFLOW.md docs/BACKLOG/README.md docs/DOCS_CHECKLIST.md docs/archive/BACKLOG/README.md docs/archive/BACKLOG/TR-006-docs-maintainer-checklist.md docs/archive/BACKLOG/TR-010-planning-index-consistency-review.md docs/design/README.md docs/design/TR-010-planning-index-consistency-review.md docs/legends/TR-truth.md
  • git diff --check
  • pre-commit eslint
  • pre-push eslint
  • npm test

Summary by CodeRabbit

  • Documentation
    • Introduced a Planning Index Consistency Review process to keep live backlog, design history, archived backlog, and legend summaries aligned.
    • Added a landed design record describing scope, triggers, non‑goals, and minimum alignment checks.
    • Integrated the review into maintainer and contributor checklists with explicit verification steps.
    • Updated workflow guidance to trigger reviews on planning-surface changes and drift, and archived the consumed backlog item.
    • Clarified legend framing to reflect the new active review process.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 30, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0f007867-a660-4f30-87b9-559a08e5f9e6

📥 Commits

Reviewing files that changed from the base of the PR and between 3f93751 and dd02a7f.

📒 Files selected for processing (1)
  • WORKFLOW.md
✅ Files skipped from review due to trivial changes (1)
  • WORKFLOW.md

📝 Walkthrough

Walkthrough

This PR adds a landed "Planning Index Consistency Review" design record and integrates it into workflow, contributor, and maintainer checklist docs; it moves TR-010 from backlog to landed design and archive, and fixes relative links in archived backlog documents.

Changes

Cohort / File(s) Summary
Core design doc
docs/design/TR-010-planning-index-consistency-review.md
New landed Truth/design document defining the Planning Index Consistency Review: scope, triggers, non-goals, minimum alignment matrix, implementation outline, and verification approach.
Workflow & checklist integration
WORKFLOW.md, docs/DOCS_CHECKLIST.md, CONTRIBUTING.md, CHANGELOG.md
Added Planning Index Consistency Review guidance: trigger conditions, non-cadenced scheduling, required confirmations, checklist/integration notes, and a changelog entry.
Planning surface index updates
docs/BACKLOG/README.md, docs/design/README.md, docs/archive/BACKLOG/README.md, docs/legends/TR-truth.md
Removed TR-010 from current backlog, added it to landed design docs, archived the backlog entry with landed link, and updated Truth legend entries and focus phrasing.
Archive link fixes
docs/archive/BACKLOG/TR-006-docs-maintainer-checklist.md, docs/archive/BACKLOG/TR-010-planning-index-consistency-review.md
Adjusted relative Markdown links (from ../... to ../../...) so references to Truth and invariant docs resolve correctly.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • docs: add docs maintainer checklist #28: Modifies the same documentation surfaces (workflow, checklist, contributing, changelog, and planning indexes) and appears to integrate similar checklist/workflow items for planning-index consistency.

Poem

🐰 I hopped through README fields today,
Where backlog, legend, design all sway.
I nudged TR-010 to landed light,
Checked links, checklist, and set things right.
A tidy garden of indexes—hip, hooray!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add planning index consistency review' accurately summarizes the main change: introducing a planning index consistency review process across documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/tr-010-planning-index-consistency-review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
WORKFLOW.md (1)

157-176: Clear triggers and actionable confirmations.

The new Planning Index Consistency Review section provides specific triggers for when to run the review and a well-defined set of minimum confirmations. The integration into the workflow is logical and practical.

One minor observation: Line 175 references "empty-state wording" and "existing house style" without defining these terms or linking to examples. While this may be clear to current maintainers, consider adding a brief definition or cross-reference to help contributors understand what qualifies as consistent "empty-state wording."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@WORKFLOW.md` around lines 157 - 176, Update the "Planning Index Consistency
Review" section to clarify the terms "empty-state wording" and "existing house
style": add one-sentence definitions or a cross-reference (e.g., link to a style
guide or an "Writing & UI copy" section) so contributors know the expected tone
and examples; specifically mention the section title "Planning Index Consistency
Review" and the phrases "empty-state wording" and "existing house style" so you
can locate and edit the text and either inline a short definition or add a link
to the canonical style/example resource.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/design/TR-010-planning-index-consistency-review.md`:
- Around line 121-131: Add the missing TR-010 entry to CHANGELOG.md to complete
Step 4 of the implementation outline: open CHANGELOG.md and append a new entry
titled "TR-010 — Planning Index Consistency Review" that summarizes the change
(doc added, checklist/workflow/contributing updated, backlog archived) and
includes the cycle/date and any relevant links back to
docs/design/TR-010-planning-index-consistency-review.md; ensure the entry
follows the existing CHANGELOG.md formatting and style so it appears consistent
with other entries.

---

Nitpick comments:
In `@WORKFLOW.md`:
- Around line 157-176: Update the "Planning Index Consistency Review" section to
clarify the terms "empty-state wording" and "existing house style": add
one-sentence definitions or a cross-reference (e.g., link to a style guide or an
"Writing & UI copy" section) so contributors know the expected tone and
examples; specifically mention the section title "Planning Index Consistency
Review" and the phrases "empty-state wording" and "existing house style" so you
can locate and edit the text and either inline a short definition or add a link
to the canonical style/example resource.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c55bd55a-959b-4451-84e7-91e5a5298be1

📥 Commits

Reviewing files that changed from the base of the PR and between a01b0e7 and 3f93751.

📒 Files selected for processing (11)
  • CHANGELOG.md
  • CONTRIBUTING.md
  • WORKFLOW.md
  • docs/BACKLOG/README.md
  • docs/DOCS_CHECKLIST.md
  • docs/archive/BACKLOG/README.md
  • docs/archive/BACKLOG/TR-006-docs-maintainer-checklist.md
  • docs/archive/BACKLOG/TR-010-planning-index-consistency-review.md
  • docs/design/README.md
  • docs/design/TR-010-planning-index-consistency-review.md
  • docs/legends/TR-truth.md
💤 Files with no reviewable changes (1)
  • docs/BACKLOG/README.md

@flyingrobots
Copy link
Copy Markdown
Member Author

Addressed the remaining CodeRabbit nit in WORKFLOW.md with commit dd02a7f.

  • clarified what "empty-state wording" and the existing house style mean in the Planning Index Consistency Review section
  • kept the guidance anchored to a concrete in-repo example: - none currently in docs/design/README.md

@coderabbitai review please 🥕

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 30, 2026

@flyingrobots Thanks for the update! The clarification around empty-state wording and anchoring it to the concrete - none currently example sounds like a solid improvement. Triggering a review now! 🥕

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@flyingrobots flyingrobots merged commit fa3b9bc into main Mar 30, 2026
6 checks passed
@flyingrobots flyingrobots deleted the docs/tr-010-planning-index-consistency-review branch March 30, 2026 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant