Source
Claude Discord — #show-and-tell, received during v1.0-beta launch week.
Feedback (verbatim)
Sorry but I think one skill is not enough for a good spec driven
development workflow. I think there should be at least:
- Creating spec based on research & user input
- Creating an implementation plan out of the spec
- Implementation
- Code Review
Even if you have these skills up and running there are many other
design questions like format and process of handovers, subagent
designs, parallelization of work, efficient research, gradual update
of project overviews, human-in-the-loop interactions, working with
worktrees and git, token efficiency...
A one skill SDD workflow will maybe work for little adjustments /
bugfixes but will fail when creating bigger features or whole projects.
Unfortunately your approach is not taking context rot into account and
it is a bad context engineering design. Please check out the other SDD
frameworks like superpowers, GSD, BMAD for reference.
Assessment
Valid on: context rot (CONTEXT.md is lightweight vs GSD's approach),
scope positioning (skill is spec generation, not full orchestration).
Category error on: comparing a spec layer to full workflow frameworks.
Action taken
Source
Claude Discord — #show-and-tell, received during v1.0-beta launch week.
Feedback (verbatim)
Assessment
Valid on: context rot (CONTEXT.md is lightweight vs GSD's approach),
scope positioning (skill is spec generation, not full orchestration).
Category error on: comparing a spec layer to full workflow frameworks.
Action taken