Skip to content

docs(sdk): Add Linear project description template#17861

Open
christophaigner wants to merge 15 commits into
masterfrom
christophaigner/docs/project-issue-template-improvements
Open

docs(sdk): Add Linear project description template#17861
christophaigner wants to merge 15 commits into
masterfrom
christophaigner/docs/project-issue-template-improvements

Conversation

@christophaigner
Copy link
Copy Markdown
Member

@christophaigner christophaigner commented May 22, 2026

DESCRIBE YOUR PR

Preview is here.

Expands the Managing Linear Projects playbook with more prescriptive guidance on project setup and close-out.

Changes:

  • Project fields: split into MUST (title, initiative, lead, status, target date, team, description, resources) / SHOULD (customers, milestones)
  • Project description template: replaced the prose description with a copyable markdown template with inline comment prompts (summary, customer-facing changes, why, expected outcomes, in/out of scope, dependencies, risks, DoD)
  • Closing Out — Artifact Checklist: bullet list of artifacts to verify before closing (public docs, develop docs, sentry-conventions, sentry-wizard, Sentry CLI, public samples, in-product prompts, dashboards)
  • Closing Out — Communication Checklist: marketing, Vanguard, blog posts, changelog
  • Closing Out — Follow-Up: post-launch performance check and GA promotion (scoped to user-facing features)
  • planning-scoping.mdx: added a cross-reference from the project-level DoD to the new artifact checklist

Once merged, we can also add a Linear project template for it.

IS YOUR CHANGE URGENT?

  • None: Not urgent, can wait up to 1 week+

PRE-MERGE CHECKLIST

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

Made with Cursor

…book

Add a structured project description template with copyable markdown,
split required project fields into MUST/SHOULD/MAY tiers, and expand
the Closing Out section with an artifact checklist, communication
checklist, and follow-up reminders. Also add a cross-reference from
the planning-scoping DoD standard to the new artifact checklist.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 22, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
develop-docs Ready Ready Preview, Comment Jun 2, 2026 8:40am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
sentry-docs Ignored Ignored Preview Jun 2, 2026 8:40am

Request Review

christophaigner and others added 5 commits May 26, 2026 16:14
The dash placeholders inside the markdown code block were being rendered
as list items on the page, breaking the visual appearance of the template.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Move artifact and communication checklists from a separate Closing Out
section into the project description template as grouped sub-sections
(Have we updated / Have you thought about / follow-up issues). Update
the cross-reference in planning-scoping.mdx accordingly.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
christophaigner and others added 2 commits June 1, 2026 11:24
Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@christophaigner christophaigner marked this pull request as ready for review June 1, 2026 09:26
@christophaigner christophaigner changed the title docs(sdk): Expand project setup and close-out guidance in Linear playbook docs(sdk): Add Linear project description template Jun 1, 2026
@christophaigner christophaigner requested a review from mydea June 1, 2026 09:27
- [ ] In-product prompts/onboarding
- [ ] Internal adoption/usage dashboards

### Have you thought about doing a
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this could also be automated ... once checked here ... create a Linear issue for it

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Definitely, we can have a look at this in a follow-up then 👍🏻

Summary is a dedicated field in Linear (below the title), so it belongs
in the required attributes list rather than inside the description
template.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@dingsdax
Copy link
Copy Markdown
Contributor

dingsdax commented Jun 1, 2026

another thing that came to my mind, is that for almost all SDK alignment projects ... the template also applies to the initiative and we usually just point to the initiative description, assets b/c the per SDK differences are mostly minimal

Copy link
Copy Markdown
Contributor

@coolguyzone coolguyzone left a comment

Choose a reason for hiding this comment

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

LGTM!

Co-authored-by: Alex Krawiec <alexanderkrawiec@gmail.com>
For projects under a shared initiative, the per-SDK description can
reference the initiative and only document SDK-specific deviations.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@christophaigner
Copy link
Copy Markdown
Member Author

another thing that came to my mind, is that for almost all SDK alignment projects ... the template also applies to the initiative and we usually just point to the initiative description, assets b/c the per SDK differences are mostly minimal

@dingsdax agreed, what do you think about 0b5cf4e?

Copy link
Copy Markdown
Contributor

dingsdax commented Jun 2, 2026

nice 👍


- **Customers**: link relevant customer accounts or support tickets that motivated the work
- **Resources**: add relevant references (especially for larger initiatives) — design documents ([RFC](https://github.com/getsentry/rfcs), DACI, PRFAQ), Slack channels, related projects, and so on
- **Milestones**: define intermediate delivery milestones for longer projects to track progress incrementally
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Maybe also linking to existing/creating new initiatives if required?

Use this template as a starting point for the project description. For cross-SDK rollout projects where the initiative already covers the shared context (motivation, scope, outcomes), the per-SDK project description can reference the initiative and only document SDK-specific deviations (e.g., different scope, additional risks, platform-specific dependencies).

```markdown
## Why are we doing this?
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Including customer signals/anecdotes is usually what helps me understand the issues the best. Could be a smaller comment/addition here.

## Risks
<!-- What's most likely to go wrong? What's the mitigation? -->

## Definition of Done
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we want to template this, or allow every project to define their own definition of done - e.g. closed issues, deployed, tested etc?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looking at the section below it looks like there is already a section for project-specific ones?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sdk-develop-docs PRs touching develop-docs/sdk

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants