Quickstart path in bootstrap — opinionated one-command setup

[rucka]

Story Statement

As a new team adopting pair
I want a Quickstart path in bootstrap — an opinionated default config installable in one command
So that setup takes minutes instead of the full guided interview, while the complete guided bootstrap remains available for teams that want it

Where: pair-process-bootstrap, extended with a quick-mode entry point per the Guided/Quick Setup Convention (story #276)

Epic Context

Parent Epic: Skill marketplace + Quickstart + external KB scaffold #213
Status: Refined
Priority: P0 (Must-Have)

Status Workflow

• Refined: Story is detailed, estimated, and ready for development
• In Progress: Story is actively being developed
• Done: Story delivered and accepted

Acceptance Criteria

Functional Requirements

Given-When-Then Format:

1. Given an empty repository
   When a developer invokes pair-process-bootstrap in quick mode
   Then the project reaches a first workable story in under 10 minutes, with standard quality gates and PM defaults installed, no interview

2. Given the same empty repository
   When a developer invokes pair-process-bootstrap without requesting quick mode
   Then the existing full guided interview runs unchanged — quick mode is additive, never a replacement for the guided path

3. Given quick mode's resolution mechanism
   When it decides what to install
   Then it follows the Guided/Quick Setup Convention (story Guided/Quick Setup Convention — unify interactive vs default resolution across setup skills #276) exactly — KB-sensible defaults, no bespoke Quickstart-specific resolution logic

4. Given a project bootstrapped via quick mode
   When a developer later wants to change a default
   Then every default quick mode installed is a normal adoption file, editable the same way as if the guided path had produced it — quick mode produces no special, harder-to-edit state

Business Rules

• Quick mode is additive to pair-process-bootstrap, not a separate skill — one entry point, two resolution depths (per the Guided/Quick Setup Convention)
• Quick mode never skips writing adoption files that guided mode would write for the same defaults — the only difference is whether the developer is asked or defaults are silently accepted
• "First workable story in under 10 minutes" is validated as a timed scenario, not just asserted

Edge Cases and Error Handling

• Project already partially configured: quick mode detects existing adoption files (same detection each composed capability — e.g. pair-capability-setup-gates — already performs) and confirms rather than overwriting, exactly as guided mode does
• A required decision has no safe KB default (e.g., PM tool choice, if genuinely ambiguous): quick mode still asks that one question rather than guessing — quick mode reduces questions to the genuinely-defaultable ones, it does not eliminate every question unconditionally

Definition of Done Checklist

Development Completion

• All acceptance criteria implemented and verified
• pair-process-bootstrap SKILL.md extended with a quick-mode entry per the Guided/Quick Setup Convention
• Code review completed and approved
• Documentation updated — docs site (Quickstart section, cross-linked from Getting Started)

Quality Assurance

• Timed onboarding test: empty repo → first workable story via quick mode, in under 10 minutes
• Confirm guided mode (no quick-mode argument) is unaffected — full regression of the existing bootstrap flow

Story Sizing and Sprint Readiness

Refined Story Points

Final Story Points: 3 (M)
Confidence Level: Medium
Sizing Justification: composes an already-existing skill (pair-process-bootstrap) plus the Guided/Quick Setup Convention (dependency); most of the complexity is in correctly identifying which of bootstrap's existing questions have safe KB defaults, not in new mechanism design

Sprint Capacity Validation

Sprint Fit Assessment: yes, single sprint
Total Effort Assessment: fits — Yes (assuming the Guided/Quick Setup Convention story lands first)

Dependencies and Coordination

Story Dependencies

Prerequisite Stories: Guided/Quick Setup Convention (story #276) — Quickstart composes its resolution mechanism directly, not a bespoke one
Dependent Stories: none

Validation and Testing Strategy

Acceptance Testing Approach

Testing Methods: timed onboarding test on a genuinely empty repo (per the epic's own KPI: "Time to first workable story on empty repo — Target: <10 minutes via Quickstart"); regression pass on the existing guided bootstrap flow to confirm no behavior change there
Test Data Requirements: a scratch empty repository (outside the monorepo, per this project's established manual-test convention of using a $WORKDIR outside the repo)

Notes and Additional Context

Refinement Session Insights: Originally scoped around a "poc profile" (D2) that turned out to depend on the not-yet-built process-profile mechanism (#251); descoped from this story during design discussion — Quickstart now depends only on the Guided/Quick Setup Convention, which is independently buildable. If/when #251's process-profile concept lands, Quickstart can adopt it as an additional refinement, not a blocking prerequisite.
Documentation Links: Requirements R9.1 · Decision D2 · pair-requirements-triage.md G11 section

Technical Analysis

Implementation Approach

Technical Strategy: extend pair-process-bootstrap's existing algorithm with a quick-mode branch that resolves each step's decision via the Guided/Quick Setup Convention instead of asking; reuse bootstrap's existing composed skills (pair-capability-setup-pm, pair-capability-record-decision, assess-*) unchanged — only the resolution depth changes, not which skills are composed
Key Components: pair-process-bootstrap SKILL.md (quick-mode branch); no new skill file
Integration Points: Guided/Quick Setup Convention (resolution mechanism); existing bootstrap composition (pair-capability-setup-pm, pair-capability-setup-gates, pair-capability-record-decision)

Technical Requirements

• Quick mode must produce the same adoption-file shape guided mode would for the same defaults — no quick-mode-only file format
• Timed test must be reproducible (documented steps, not just "it felt fast")

Technical Risks and Mitigation

Risk	Impact	Probability	Mitigation Strategy
Some of bootstrap's existing questions don't have a safe, universally-correct KB default	Medium	Medium	Quick mode only defaults genuinely-defaultable decisions (per the Guided/Quick Setup Convention's own guidance); ambiguous ones are still asked
10-minute target missed on slower environments (network-bound skill install, etc.)	Low	Low	Timed test documents environment assumptions; target is a KPI to track, not a hard gate that blocks merge

Task Breakdown

Checklist

• T1 — Identify which of bootstrap's existing decision points have a safe KB default vs. which must still be asked even in quick mode
• T2 — Add the quick-mode entry/branch to pair-process-bootstrap SKILL.md, resolving defaultable decisions per the Guided/Quick Setup Convention
• T3 — Timed onboarding test (empty repo → first workable story, <10 min) + guided-mode regression check + docs site update

Dependency Graph

T1 → T2 → T3

AC Coverage

Task	AC1	AC2	AC3	AC4
T1	✓			✓
T2	✓	✓	✓	✓
T3	✓	✓