Conversation
The draft plan is a collaborative process to build a standalone specification that leaves implementation with zero creative latitude. Key clarifications: - Draft serves two purposes: enrichment (adding missing detail through collaboration) and filtering (removing noise/speculation/hallucination) - Output must be standalone - contains everything needed for formal planning - Anti-pattern: summaries that create "another useless file" - Good vs bad draft examples added with concrete detail - New "No Room for Creativity" principle in guidelines - Updated document format with Specification section as the deliverable
Key changes: - Remove "zero creative latitude" and "no room for interpretation" language - Draft captures WHAT/WHY/edge cases/acceptance - HOW is optional and varies - Amount of detail depends on the feature - some need detailed approach, others just need clear definition - Implementation can take charge or collaborate - not just mechanical execution - Good draft example now shows guidance without being prescriptive - Draft process is about finding the RIGHT level of detail, not maximum detail
Reframe guidance as positive patterns instead of showing what not to do: - Replace "Bad Draft" / "Good Draft" with single example of complete draft - Replace "Bad" / "Good" comparisons with positive examples only - Reframe "Anti-Hallucination" as "Building Through Collaboration" - Keep absolute rules (don't write code during planning) but remove soft guidance framed as negatives
- Remove draft specification example (draft will vary by task) - Remove task examples and other constraining examples - Remove "team familiarity" reference - this is user + Claude collaboration
Follow Anthropic's skill-creator guidance: - Keep SKILL.md lean, detailed info in references - Avoid duplication between SKILL.md and reference files - Progressive disclosure: essentials in SKILL.md, details on demand Removed duplicated content (already in reference files): - Detailed "What to capture" list -> planning-conversations.md - Detailed commit rules -> guidelines.md, planning-approach.md - Plan contents details -> template.md - Implementation flow -> guidelines.md, output adapters Kept essential rules concise in SKILL.md with clear links to references.
Major restructure to separate draft and formal planning clearly: SKILL.md (52 lines): - Lean with clear personality (architect + product owner + documenter) - CRITICAL: Must ask user which path before proceeding - Path A: Draft planning → draft-planning.md - Path B: Formal planning → formal-planning.md → output adapter New reference files: - draft-planning.md: Complete draft planning workflow - formal-planning.md: Common formal planning process Merged/removed: - template.md → merged into output-local-markdown.md - planning-approach.md → split between draft/formal - guidelines.md → split between draft/formal - planning-conversations.md → replaced by draft-planning.md Key change: Agent must ASK user which path, not decide themselves.
leeovery
deleted the
claude/clarify-draft-planning-01UjpN7edJfbhZeSAqxWx15E
branch
leeovery
added a commit
that referenced
this pull request
Apr 20, 2026
…g-queue fail, pause stdin after rebuild confirm Three targeted internal cleanups: - withRetry now lets TypeError / ReferenceError / SyntaxError through immediately instead of waiting 7s of backoff. A typo shouldn't burn retry budget before the real trace reaches the developer. (deferred #9) - cmdIndexBulk catch now writes err.stack to stderr after the summary line. Debug info is no longer lost just because the user was piping stdout. (deferred #10) - cmdRebuild's readStdinLine now pauses stdin after consuming the confirmation line. Irrelevant for the CLI but prevents a library consumer from keeping the event loop alive on an idle stream. (deferred #16) Closes deferred-issues #9, #10, #16.
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
2 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.
The draft plan is a collaborative process to build a standalone specification
that leaves implementation with zero creative latitude. Key clarifications:
collaboration) and filtering (removing noise/speculation/hallucination)