feat: add feature-planner skill for non-technical contributors#525
Merged
cb-ekuersch merged 3 commits intomasterfrom Mar 20, 2026
Merged
feat: add feature-planner skill for non-technical contributors#525cb-ekuersch merged 3 commits intomasterfrom
cb-ekuersch merged 3 commits intomasterfrom
Conversation
A guided workflow that helps designers and PMs turn feature ideas into detailed technical implementation plans. Two-phase approach: a plain-language discovery interview followed by a thorough engineering plan with Linear issue creation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Collaborator
✅ Heimdall Review Status
✅
|
| Code Owner | Status | Calculation | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ui-systems-eng-team |
✅
1/1
|
Denominator calculation
|
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
haoruikun-cb
approved these changes
Mar 20, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
What changed? Why?
When a non-technical member of the team vibe-codes a contribution to this repo, it can produce changes that are difficult to review. With their current limited technical knowledge, it can be difficult for these contributors to catch mistakes the agent makes along the way and steer it in different directions.
This PR introduces the start of a new process in which participants first work with the agent to create a detailed implementation plan that is automatically uploaded to Linear for an engineer to review. Having an engineer sign off on the plan prior to kicking off the work and iterating on design will drastically reduce the complexity of PRs opened by these contributors.
In addition to producing high quality PRs, this process will help non-technical contributors iterate much faster due to the agent-written implementation plan. For an analogy, imagine starting a road trip to a new, distant location with only a paper map. This process gives the driver GPS.
Sample PR: #524
Skill description
A guided workflow that helps designers and PMs turn feature ideas into detailed technical implementation plans. Two-phase approach: a plain-language discovery interview followed by a thorough engineering plan with Linear issue creation. Linear issues are created under the CDS team and will contain the full implementation plan.
Sample Linear issue from a run: https://linear.app/coinbase/issue/CDS-1727/motion-token-playground-for-docs-site
Root cause (required for bugfixes)
UI changes
Testing
How has it been tested?
Testing instructions
Illustrations/Icons Checklist
Required if this PR changes files under
packages/illustrations/**orpackages/icons/**Change management
type=routine
risk=low
impact=sev5
automerge=false