feat(po): plan-definition — guided discovery phase upstream of plan-backlog (#73, v1) - #79
Open
atamanvega wants to merge 2 commits into
Open
atamanvega wants to merge 2 commits into
atamanvega wants to merge 2 commits into
Conversation
…acklog (#73, v1) Adds the most upstream step of the PO workflow: define the problem before turning it into a backlog. A guided, Socratic pass frames the problem (users, outcome, why-now, constraints, success metrics, risks, non-goals) with proposed answers to confirm/adjust, explores 2–4 solution directions with trade-offs, and produces an approved product definition — a definition doc, not tickets. Renders as a navigable artifact on hosts that support it (reusing #74's doctrine), Markdown elsewhere. The definition feeds plan-backlog, whose framing step is now lighter when a definition is handed in (confirm, don't re-derive). Ships the same trio as plan-backlog: - skills/plan-definition/SKILL.md — portable playbook (all hosts) - commands/plan-definition.md — Claude Code guided command - agents/plan-definer.md — discovery orchestrator (intake + draft engine) Facilitate-never-decide, approval-gated, no fabrication. v1 for team review (open design questions left to refine in #73). Full flow: define → backlog → ticket → PR → follow-ups. Bundle rebuilt (13 skills), version bumped, README + CHANGELOG updated. Kit → 0.19.13. 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
|
From the kit's own pr-reviewer pass on #79: - FigJam accuracy: figma-fetch only reads /design and /file URLs, not FigJam /board/ — stop implying it fetches boards. The three new files now say figma-fetch covers Figma designs and a FigJam board's content is taken as pasted text (v1 read-only context, nothing written back). - Loop-phrase consistency: keep plan-backlog's own loop as "idea → backlog → ticket → PR" in the README paragraph (plan-backlog genuinely starts from an idea); "define → ..." stays in the plan-definition paragraph and the full-flow CHANGELOG line. - Drop the unused dev-kit-setup skill from plan-definer's frontmatter — it touches no tracker and creates no tickets. Bundle re-synced (source/bundle byte-identical); validator + 35 tests pass. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Closes the design work in #73 with a v1 implementation. From @santielizondo's idea.
The gap it fills
plan-backlogstarts from a defined problem. The hardest, most valuable part often comes before that: defining the problem.plan-definitionis that phase — a guided, Socratic discovery step that produces a product definition, which then feedsplan-backlog.Full flow:
/plan-definition(define) →/plan-backlog(backlog) → ticket → PR → follow-ups.What it does
figma-fetch(incl. FigJam/board/as read-only context in v1).plan-backlog, whose framing is then lighter (confirm, not re-derive).Shape
Same trio as
plan-backlog, so it's portable and consistent:skills/plan-definition/SKILL.mdcommands/plan-definition.mdagents/plan-definer.mdPlus:
plan-backlogSKILL now runs a lighter framing when a definition is handed in.Design decisions taken for v1 (open questions from #73 — refine away, @santielizondo)
/plan-definition), not a mode of plan-backlog — different output (a definition doc, not a backlog).docs/definitions/<slug>.mdon request. No Confluence/whiteboard write-back in v1.Guardrails (same doctrine)
Facilitate-never-decide · no fabrication (a thin spark is drawn out with questions, not invented) · approval-gated · no tickets here (that's plan-backlog) · secrets/PII watch.
Verification
node scripts/build-codex-plugin.mjs→ 13 skills synced, version 0.19.13node scripts/validate-codex-plugin.mjs→ validnode --test scripts/*.test.mjs→ 35/35 passgit diff --exit-codeclean)Docs-in-sync: README (From idea to backlog, What's inside, Day-to-day, flow → define → backlog → ticket → PR), CHANGELOG. Kit → 0.19.13.
🤖 Generated with Claude Code