starting-point

Use when a request prescribes a method, tool, metric, or artifact that may not reach the result the user described, or when doing the request as written would leave that result unproved: "A/B test the signup button color" for a conversion problem, "add a cache" for a slow page, "the focused tests passed, announce the release". Also use when a stated constraint contradicts itself, when an unknown fact would have to be invented to finish, or when an external or irreversible step needs an authorization decision. Keywords: right approach, wrong metric, root cause, outcome versus output, what counts as done, proof, is this worth doing. Not for a literal edit, format, translation, or lookup whose method is the deliverable. Not a replacement for the design, debugging, research, or writing method that performs the work. Use the reify skill instead when the request is still too vague to have any method or outcome yet.

Version

0.1.0

License

MIT