chore: publish artifact as part of plan-epic final report - #301
Merged
Conversation
Carries over the epic-breakdown artifact pattern used for MON-207 into the skill itself so future /plan-epic runs report visually too.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🧪 dbt data-health check — ✅ passedValidates prod data health. A failure means current prod data is stale/broken, not necessarily that this PR is wrong. |
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
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
Adds an artifact-publishing step to the
/plan-epicskill's final report so every epic decomposition also renders a visual dependency-chain breakdown, not just plain text.Why
Split out of #300 (MON-214) at that PR's own review's request — this doc-only change to
.claude/skills/plan-epic/SKILL.mdis unrelated to MON-214's scope and belongs in its own PR.Changes
.claude/skills/plan-epic/SKILL.md: step 7 now also publishes an HTML Artifact of the sub-issue plan (dependency-ordered cards linking to the created Linear issues), loadingartifact-designfirst and reusing the same scratchpad file path across a planning session so re-publishing after Linear writes updates the same URL.Testing
Not applicable — this only changes Claude Code skill instructions, no application code.
Risks / Notes
None. No app code, no deploy surface.
Breaking Changes
None.