Rename/repurpose the "🦢 Drafting" board => "🦢 Product design intake & outtake"

[noahtalerman]

This PR updates the handbook to reflect the "🦢 Drafting" board => "🦢 Product design intake & outtake" change.

• We'll now use the intake & outtake board for only new request and bug triage (intake) and confirm and celebrate (outtake).
• Stories going through drafting are tracked on the product group boards.

Why?

• Tracking stories on both the product group boards and the "🦢 Drafting" board creates extra paperwork that leads to missed updates, which leads to confusion.
• Contributors already move stories on their product group's board. The people who need to see these issues day-to-day (Product Designers and Engineers) live there. So, stories often didn't get moved on the drafting board too. We don't need two boards to keep in sync.

Summary by CodeRabbit

• Documentation
  • Clarified product design review instructions to focus on in-progress stories in the “Drafting” column.
  • Updated user story review guidance to reference stories that completed the product checklist.
  • Corrected the spelling of “Engineering Manager.”

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.79%. Comparing base (b44343c) to head (416facf).

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #51867   +/-   ##
=======================================
  Coverage   69.79%   69.79%           
=======================================
  Files        4072     4072           
  Lines      265453   265453           
  Branches    14240    14240           
=======================================
  Hits       185285   185285           
  Misses      63978    63978           
  Partials    16190    16190           

Flag	Coverage Δ
android	51.46% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[noahtalerman]

• New request and bug triage uses an ~inbox label instead of the drafting board.
  • The bug report and feature request issue templates now apply ~inbox automatically. The Head of Product Design / QA Manager triage by that label and add the correct product group label (which moves the issue into that board's Inbox column), then remove ~inbox.

FYI @AndreyKizimenko please let me know if this won't work

[noahtalerman]

• Confirm and celebrate happens on each product group's board.
  • After we merge this PR, we'll add a "🎉 Confirm & celebrate" column to the product group board columns table. Release and milestone-close steps (handbook/engineering/releases.md, android/RELEASE.md) now moves them to "Confirm and celebrate" on their own board instead of routing through the drafting project.
• tools/github-manage (workflows.go, projects.go, ui.go, hotkeys.go): removed the sprint-kickoff/kick-out-of-sprint workflows and drafting-project plumbing that existed only to move issues to/from the drafting board.
  • BulkMilestoneClose now resolves each issue's product group board from its #g-* label (via new ProjectIDForLabels) and sets "confirm and celebrate" status there directly.
  • Also updated the ProjectLabels map to the current set of product group boards/labels.

@lukeheath I asked Claude to update the BulkMilestoneClose, when you get the chance, can you please help me review the updates to make sure they'll work.

Also FYI re removing tools from github-manage that were there for moving issues from the drafting board. Please let me know if we still need those.

[noahtalerman]

FYI @melpike @marko-lisica @Leanngove

[noahtalerman]

• So, this PR updates the handbook to use a "Product design intake & outtake." We'll use this board for new request and bug triage (intake) and confirm and celebrate (outtake).

@AndreyKizimenko new plan: just a new name for the board. Bug triage process (including :product label) don't change.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: db0a077b-8692-4cc3-8192-39e6b9d943e3

📥 Commits

Reviewing files that changed from the base of the PR and between b44343c and 416facf.

⛔ Files ignored due to path filters (5)

• android/RELEASE.md is excluded by !**/*.md
• handbook/company/product-groups.md is excluded by !**/*.md
• handbook/engineering/README.md is excluded by !**/*.md
• handbook/engineering/releases.md is excluded by !**/*.md
• handbook/product-design/README.md is excluded by !**/*.md

📒 Files selected for processing (1)

• handbook/product-design/product-design.rituals.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• handbook/product-design/product-design.rituals.yml

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

Walkthrough

Updated two product design handbook rituals. The Product design review now checks that only in-progress stories remain in the “Drafting” column for each product group. The User story review now references stories that completed the product checklist and are ready for review. The change also corrects “Mananger” to “Manager.”

Merge Risk: ⚪ Minimal · up to 416fa

This change updates handbook references for the product design intake and outtake workflow without changing product behavior or runtime systems. No actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description explains the board change and its rationale, but it omits the required related issue field and checklist sections, including testing and QA status.	Add the required template sections. Provide a related issue or remove the field if not applicable. Mark each applicable checklist item, remove non-applicable items, and document testing and manual QA results.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states the board rename and repurposing, which matches the pull request objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch remove-drafting-board

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}