sciman-top Draft Spec
Turn the context already available into a concise, reviewable Markdown draft.
Output
Return the draft in the response with these sections:
- Problem statement
- Goals and non-goals
- User stories or user-visible outcomes
- Requirements and implementation decisions
- Acceptance criteria and test strategy
- Risks, assumptions, and open questions
- Publication handoff (what still needs approval or tracker configuration)
Use repository terminology and existing ADRs when they are available. Separate facts, decisions, assumptions, and unanswered questions. Prefer observable behavior and seams over speculative file-by-file plans.
Side-effect boundary
This is a draft-only skill. Do not call an issue tracker, create labels or
links, invoke to-spec/to-tickets, or create or modify repository files.
If the user later asks to publish the draft, hand off to an explicit
$to-spec invocation after the user has reviewed it.