docs(sdk): Planning & Scoping standard & Managing Linear Project Management Playbook#16589
Merged
docs(sdk): Planning & Scoping standard & Managing Linear Project Management Playbook#16589
Conversation
Convert the triage process guidelines into a playbook at coordination/triaging.mdx, following the spec format used by other coordination playbooks. - Add triaging playbook with 4 steps: monitor intake channels, acknowledge new items (with CopyableCard response templates), normalise the issue in Linear, and route to one of four outcomes (close, resolve, accept, escalate) - Fold triage rotation and accountability requirements from the original "Principles" section into the Overview - Add abstract Resources section with internal Linear dashboard links and external reading on open source community maintenance - Update /sdk/processes/triaging/ redirect from the generic playbooks index to the specific playbook URL - Add cross-link from coordination-maintenance#triaging-sla to the new playbook - Add linear.app/getsentry and calendar.google.com to .lycheeignore as private/auth-gated resources Co-Authored-By: Claude <noreply@anthropic.com>
…ng.mdx Co-authored-by: Stephanie Anderson <stephanie.anderson@sentry.io>
…ng.mdx Co-authored-by: Stephanie Anderson <stephanie.anderson@sentry.io>
…ts playbook Add two new draft develop-docs for SDK project management: - Planning & Scoping standard (7 sections): issue quality, definition of done, project naming, design-first gate (with partner identification and risk section requirement), risk identification, spike timeboxing, and AI-assisted planning - Managing Linear Projects playbook (9 steps): required attributes, initiative taxonomy (product/alignment/maintenance), pre-implementation docs, communication channel, backlog triage, WIP hygiene, community contributions, visibility, and close-out Also fix broken #cross-sdk-coordination-protocol anchors in four existing playbooks and add cross-links throughout the affected docs. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Replace flat numbered steps with three named phases — Setup (steps 1-5, sequential), During the project (ongoing responsibilities), and Closing out (sequential steps). Steps 6-8 were not sequential and are now correctly represented as continuous practices rather than one-time actions. Co-Authored-By: Claude <noreply@anthropic.com>
…rojects Allow re-using an existing channel and update the Slack channel naming example to reflect common conventions (#proj-<name>, #team-sdks). Co-Authored-By: Claude <noreply@anthropic.com>
Rename the playbook to "Project Management in Linear" and expand scope to cover the full Linear hierarchy — initiatives, cross-SDK sub-initiatives, projects, and standalone backlog issues. Add a new "The Linear hierarchy" table and an "Initiatives" section with a three-category decision table (product feature / cross-SDK alignment / SDK maintenance) and guidance on sub-initiatives for cross-SDK rollouts. Restructure the Projects section into three named phases: Setup (sequential steps), During the project (ongoing responsibilities), and Closing out. Add a new "Standalone issues and backlog work" section that applies the same WIP limits and issue quality rules to non-project work, with guidance on when to escalate to a project. Add managing-issues.mdx boilerplate for the standalone issue workflow (steps to be filled in as a follow-up). Co-Authored-By: Claude <noreply@anthropic.com>
The playbook was scoped to GitHub issues and PRs, but triage covers any incoming item regardless of channel — Discord, Slack, Linear, etc. Items may also arrive without a pre-existing Linear issue. Update language throughout to use "item" as the generic term, clarify that a Linear issue must be created during normalisation if one doesn't exist, and make the SLA apply regardless of intake channel. Co-Authored-By: Claude <noreply@anthropic.com>
Restructure managing-linear-projects as the canonical reference for the full Linear hierarchy. Add initiative hygiene, GitHub sync and visibility guidance (repo-named vs umbrella teams), data hygiene requirements (PII warning as Alert), Linear views recommendations, Requires Customer Signal status note, and Title Case + style guide fixes throughout. Delete managing-issues.mdx stub — issue lifecycle content is now covered inline under the Issues section of managing-linear-projects. Add sync visibility and data hygiene bullets to triaging.mdx step 3. Co-Authored-By: Claude <noreply@anthropic.com>
stephanie-anderson
approved these changes
Mar 6, 2026
Contributor
stephanie-anderson
left a comment
stephanie-anderson
left a comment
There was a problem hiding this comment.
Left some comments, but looks good otherwise!
…ng-linear-projects.mdx Co-authored-by: Stephanie Anderson <stephanie.anderson@sentry.io>
Co-authored-by: Stephanie Anderson <stephanie.anderson@sentry.io>
…ng-cross-sdk-changes.mdx Co-authored-by: Stephanie Anderson <stephanie.anderson@sentry.io>
…ng-cross-sdk-changes.mdx Co-authored-by: Stephanie Anderson <stephanie.anderson@sentry.io>
…rly-cross-sdk-retro.mdx Co-authored-by: Stephanie Anderson <stephanie.anderson@sentry.io>
…rly-cross-sdk-retro.mdx Co-authored-by: Stephanie Anderson <stephanie.anderson@sentry.io>
…cating-an-api.mdx Co-authored-by: Stephanie Anderson <stephanie.anderson@sentry.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
Add two new draft develop-docs for SDK project management, plus cross-link and
anchor fixes across existing coordination docs.
New: Planning & Scoping standard (
standards/planning-scoping.mdx,spec_status: draft)Seven sections covering the full planning lifecycle:
[Effort name] [SDK name]format for cross-SDK rollout projectslarge or multi-SDK changes; includes partner/stakeholder identification requirement.
References Building Something New at Sentry (internal).
resolved (via spike or mitigation plan) before implementation starts
sub-issues before acting on them; references
sentry-sdk-skills:linear-initiativeNew: Managing Linear Projects playbook
(
playbooks/coordination/managing-linear-projects.mdx,spec_status: draft)Nine-step lifecycle guide for project leads, from kickoff to close-out:
(product feature / cross-SDK alignment / maintenance)
References Goal Hierarchy (internal) / Great Data Capture goal.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES
Sentry Docs contributor guide
Co-Authored-By: Claude noreply@anthropic.com