Skip to content

[RUNBOOK] Phase 6 — Docs + dogfooding #56

Description

@aram-devdocs

Summary

Finish the user-facing story: publish the mdBook at plumb.aramhammoudeh.com, run
Plumb against its own site until it passes clean, publish baseline
performance benchmarks, and capture the V0 architectural decisions
as ADRs. Adds the landing site and enables GitHub Discussions.

This is the phase that flips Plumb from "works" to "launchable."

PRD references

  • PRD §15
  • PRD §16

Acceptance criteria

  • plumb.aramhammoudeh.com live and indexed, with install / quick-start / config / rule / MCP / FAQ chapters.
  • plumb lint https://plumb.aramhammoudeh.com emits zero violations (dogfooding clean).
  • Benchmarks published showing cold-start, warm-run, per-rule cost across DOM sizes.
  • Landing site live with 90%-UI problem framing + quick demo + install CTA.
  • GitHub Discussions enabled; roadmap umbrella pinned.
  • All 8 child PRs merged.

Batches

Gates run sequentially (every PR in Gate N must merge before Gate N+1 starts). Within a gate, batches are parallel. For each batch, a recommended dispatch strategy is shown — you can always pick a different shape if it fits. See .agents/rules/dispatch-strategy.md for the heuristic.

Gate Batches Tickets After
Gate 1 6A #57 #58 #59 (initial)
Gate 2 6B #60 #61 #62 Gate 1 merged
Gate 3 6C #63 #64 Gate 2 merged

Gate 1

Batch 6A — Core docs chapters

# Ticket Crate Effort Extras
#57 install + quick-start + config reference chapters docs M
#58 MCP integration cookbook (Claude Code, Cursor, Codex) docs M
#59 FAQ + troubleshooting (CSP, auth, Chromium, CSS-in-JS) docs S

Dispatch (bundle): same crate, similar effort — bundling keeps related changes atomic.

/gh-issue 57 58 59 --worktree

Advance to Gate 2 when: every PR in Gate 1 is merged.

Gate 2 after Gate 1

Batch 6B — Dogfooding + benchmarks + ADRs

# Ticket Crate Effort Extras
#60 plumb.aramhammoudeh.com demo fixture + clean lint docs L
#61 cold-start, warm-run, per-rule cost across DOM sizes ci M
#62 ADRs 0002–0004 (DTCG vs alternatives, no auto-fix, Chromium pin) docs S

Dispatch (split): touches 2 crates — split so each gets focused review.

/gh-issue 60 --worktree
/gh-issue 61 --worktree
/gh-issue 62 --worktree

Advance to Gate 3 when: every PR in Gate 2 is merged.

Gate 3 after Gate 2

Batch 6C — Branding + community

# Ticket Crate Effort Extras
#63 plumb.aramhammoudeh.com landing site (90%-UI problem + demo + CTA) docs L
#64 enable GitHub Discussions + pin roadmap + launch blog post docs S

Dispatch (cluster): mix of small and large — bundle 1 small, split 1 large to keep review <400 LOC.

/gh-issue 64 --worktree
/gh-issue 63 --worktree   # L: docs-landing-site

Phase gate follows — see below.

Phase gate

plumb.aramhammoudeh.com live AND plumb lint https://plumb.aramhammoudeh.com emits 0 violations
AND benchmarks published AND landing page live AND
cargo xtask pre-release green.

Unblocks: phase-7

How to execute

  1. Create GitHub milestone v0.6-phase-6 if it doesn't already exist.
  2. Run bash create-issues.sh from this directory to create all child issues.
  3. Dispatch /gh-issue <child-number> for each batch in order; sessions within a batch run in parallel.
  4. Close this parent issue when every child is merged and the phase gate holds.

Generated

  • Generated at: 2026-04-24T13:16:43Z
  • Source spec: docs/runbooks/phase-6-spec.yaml
  • Repo: aram-devdocs/plumb

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind:rfcDesign proposalphase-6V0 Phase 6 — docs + dogfooding

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions