Add write-design-spec PM design phase; rename spec pipeline to dev-spec - #76
Merged
Conversation
Splits the old single-pass spec skill into two phases: write-design-spec produces a PM-style design (problem, solution, observable behavior, broken into independently cuttable deliverables), while write-dev-spec (renamed from spec) covers the implementation-level "how" that follows it. The dev-spec-* rename disambiguates the existing pipeline now that "design" and "spec" are both real, distinct document types. - New write-design-spec command and its skills: gather-brief-sources, design-first-draft, design-deliverable-breakdown, design-work-items, researcher-design-review. - Renamed spec-* skills to dev-spec-* (dev-spec-first-draft, dev-spec-task-breakdown, dev-spec-task-work-items, read-dev-spec-section, researcher-dev-spec-review) and merged the document-review skills (spec-discussion, spec-readiness-review) into shared, document-type-agnostic document-discussion and document-readiness-review skills. - documentation.specs now covers the new PM design doc (_design_<slug>.md); the old dev spec category moves to the new documentation.dev-specs key (_spec_<slug>.md unchanged on disk). - add-to-spec stays a single command that branches internally by document type rather than splitting in two. - Updated all ripple references across README, researcher agent, playbook-contract, harvest-playbook, and the playbook-harvesting fixture/dry-run harness to the renamed skill names. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
build-and-test: Python test resultsStatus: ✅ Passed Test log |
jodavis
requested changes
Jul 21, 2026
- Move specs location to docs/ (design docs span the whole project) - Push stop-condition wording to gather-brief-sources: warn on an unresolved specifically-referenced source instead of treating "no tracked work item" as a stop condition in write-design-spec / write-dev-spec - Clarify independently-cuttable sizing rule: siblings may depend on one shipping before them, but never only lay groundwork for a later one; spell out the two failure modes this guards against - Move "identify related existing work items" to a new step 2 in write-design-spec, before the first draft, and have design-deliverable-breakdown reconcile against that list instead of asking fresh per-deliverable Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
jodavis
approved these changes
Jul 21, 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.
Summary
Test plan
🤖 Generated with Claude Code