feat(skills): plan-backlog — idea → well-formed backlog (#64) - #65
Merged
Conversation
) (v0.19.8) The upstream, product-owner half of the workflow: turn an idea (chat text, PDF, Word, artifact, Confluence) into a well-formed backlog — epics, INVEST user stories with Given/When/Then acceptance criteria, sub-tasks, dependencies — and create it in the configured tracker AFTER an explicit approval gate. - Discovery-first: learns the team's native hierarchy/conventions from the tracker instead of imposing one; maps a neutral model onto Jira / Linear / GitHub Issues / Azure DevOps via adapters (the write counterpart to issue-fetch). - Never creates anything before approval; grounds everything in the source (no fabricated scope/AC); watches for secrets/PII. - Created stories hand off to work-story → PR, closing idea → backlog → ticket → PR. - Bundled + version aligned (0.19.8); node --test 35/35. Design: #64. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
…64) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Sep 2, 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
1 participant
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.
Implements the v1 of #64 — the product-owner, upstream half of the kit: turn an idea/description into a well-formed backlog and create it in the configured tracker.
Closes the loop idea → backlog → ticket → PR (created stories feed
work-story).What it does (
skills/plan-backlog/SKILL.md).docxviatextutil/pandoc), an artifact, a Confluence page; Figma links →figma-fetch..claude/dev-kit.json(tracker.type) and learns the team's native hierarchy, fields, and a sample of recent issues to calibrate granularity; asks only what it can't discover.work-story).createJiraIssue+ links), Linear (MCP, Project/sub-issues), GitHub (gh issue create+ milestones/labels, read-back verified), Azure (az boards+ relations).work-story <KEY>.Guardrails
Never create before approval · discovery-first (mirror the team, don't impose) · no fabricated scope/AC · secrets/PII care · report partial failures.
Notes
issue-fetch(which reads) — no overlap with any existing skill/agent (there was no ticket-creating capability before).Verification
🤖 Generated with Claude Code