jumpstart

name	jumpstart
description	Guide a new SPK user from repository orientation to a reviewed plan, diagnosis, or design direction, with approval before implementation.

Jumpstart

The shortest path from a fresh installation to a useful first engineering artifact.

Workflow

1. Orient. Inspect repository status, instructions, source manifests, and SPK scaffold using read-only checks. If scoped agent guidance is missing, explain the PROJECT_WRITE effect and apply repository priming before continuing.
2. Get one goal. Use a goal already supplied by the user. Otherwise ask exactly one question: what do they want to build, fix, or redesign? Do not start an interview; record assumptions for non-critical gaps.
3. Route one path.
   • New behavior or architecture → apply the planning workflow.
   • Bug or regression → apply root-cause debugging without patching.
   • Interface direction → apply design-shotgun exploration without production edits.
   • Another engineering request → use the canonical SPK router.
4. Produce the first win. Return a reviewed plan, proven diagnosis with smallest fix, or comparison board with one recommendation. Run an explicit verifier pass over the artifact before presenting it.
5. Ask once before implementation. Summarize exact implementation scope, paths, tests, and effect, then ask whether to continue. Only an unambiguous yes authorizes project source changes. A hedge or silence is not approval.
6. Implement if approved. Apply the implementation or TDD workflow with the artifact as immutable input. Do not stage, commit, push, open a pull request, or deploy unless those actions were separately requested and approved.

Budget: one orientation pass, one user question, one primary workflow, one verifier, and one implementation confirmation.

Evidence Receipt

Return spk.evidence/v1 with the routed workflow, effect level, orientation artifacts, first-win artifact, verification, assumptions, approval state, risks, and next action.

Guardrails

• Never write production source before explicit implementation approval.
• A missing subagent capability is not a blocker; continue sequentially.
• Work outside git repositories and in empty repositories with reduced diagnostics.
• If the user stops, preserve only the useful orientation artifacts already disclosed.
• External writes and uninstall always remain behind their manual approval protocols.