Skip to content

samples: standardize READMEs, naming, and add template#484

Merged
bradygaster merged 2 commits intobradygaster:devfrom
diberry:squad/examples-improvements
Mar 22, 2026
Merged

samples: standardize READMEs, naming, and add template#484
bradygaster merged 2 commits intobradygaster:devfrom
diberry:squad/examples-improvements

Conversation

@diberry
Copy link
Copy Markdown
Collaborator

@diberry diberry commented Mar 21, 2026

SDK Samples Portfolio Improvements (PRD Recs #3, #8, #9)

Hey @bradygaster — the team reviewed and approved this set of improvements to the samples portfolio. This PR focuses on documentation and naming consistency — no code logic changes, just making the samples more accessible to new users.

What changed

18 files changed (17 modified, 1 new) — all in samples/

Recommendation #3: Package naming standardization

  • All 9 sample package.json files now use @squad-samples/{name} format
  • Previously: 3 different conventions (bare names, -sample suffix, @squad-samples/ scope)
  • Now: consistent @squad-samples/* across the board

Recommendation #9: Root samples/README.md overhaul

  • Before: Titled "SDK Samples Portfolio — MVP Summit" with internal planning language
  • After: Titled "Squad SDK samples" — public-facing index with prerequisites, quick start (3 commands), difficulty grid, and learning path
  • All 9 samples listed with difficulty levels and key SDK concepts

Recommendation #8: Per-sample README standardization

  • All 9 sample READMEs now follow the same template structure:
    • Prerequisites → Quick start → What you'll learn → How it works → Expected output → Key files → Next steps
  • Learning path links connect samples: hello-squad → knock-knock → hook-governance → ... → azure-function-squad
  • Microsoft Writing Style Guide applied: sentence case headings, "you" voice, contractions, active voice

New: SAMPLE-README-TEMPLATE.md

  • Template file for future sample authors to copy
  • Includes HTML comment instructions per section with length/depth guidance
  • References Microsoft Writing Style Guide principles

Why this matters

The samples are Squad's primary on-ramp for new developers. Today:

  • Root README reads like an internal sprint doc ("MVP Summit")
  • Package names use 3 different conventions
  • READMEs have inconsistent structure — no learning path, no prerequisites
  • New users can't tell where to start

After this PR:

  • Clean public-facing index says "start here, run this"
  • Consistent structure means developers know exactly where to find prerequisites, expected output, and next steps
  • Learning path guides beginners through samples in order of complexity

CI status

  • markdownlint — 0 errors (134 files checked)
  • cspell — 0 issues on all changed files
  • No code changes — existing tests unaffected

Team review

  • 🏗️ Mal (Lead) — Approved with notes
  • 📝 Book (Docs) — Approved with notes
  • 🧪 Simon (Tester) — Approved with notes
  • 🔧 River (SDK) — Approved with notes (SDK API references verified accurate)

PRD reference

Full PRD with 9 active recommendations (this PR covers #3, #8, #9) is tracked in our project management repo. Remaining recommendations (#1 pipeline split, #2 LLM test coverage, #5 demo/live separation, #10 docs site integration) planned for follow-up PRs.

@diberry
Copy link
Copy Markdown
Collaborator Author

diberry commented Mar 21, 2026

@bradygaster — team reviewed and signed off on this one (Mal, Book, Simon, River all approved). Covers PRD recs #3 (package naming), #8 (README standardization), and #9 (root README overhaul). No code logic changes — pure docs/naming improvements. All markdownlint and cspell checks pass. Ready for your review when you get a chance.

Copilot AI added 2 commits March 22, 2026 00:02
Add 31 tests defining the behavioral contract for the planned
autonomous-pipeline-core module (PRD Recommendation #1). Tests cover:

- Task→tier assignment via selectResponseTier with DEMO_CONFIG
- CostTracker per-agent accumulation across multiple agents/tasks
- Agent state transitions (idle→working→idle→done lifecycle)
- selectResponseTier routing properties (tier, modelTier, maxAgents, timeout)
- Task queue creation, role coverage, and findNextTask assignment logic
- simulateCost model contract (complexity→tokens→cost scaling)
- Core pipeline wiring without telemetry/dashboard/OTel dependencies

All 31 tests pass against current code. After the refactor splits
core logic from telemetry+dashboard, these same assertions verify
the extracted module preserves identical behavior.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Standardize all 9 package.json names to @squad-samples/* format (Rec #3)
- Rewrite root samples/README.md as public-facing index with learning path (Rec #9)
- Standardize all 9 per-sample READMEs to consistent template (Rec #8)
- Apply Microsoft Writing Style Guide across all sample documentation
- Add SAMPLE-README-TEMPLATE.md for future sample authors
- Add 31 TDD tests for autonomous-pipeline core split (Rec #1 prep)

17 files modified, 1 new file. All markdownlint and cspell checks pass.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@bradygaster bradygaster force-pushed the squad/examples-improvements branch from 5285bcd to 3f6f074 Compare March 22, 2026 07:02
Copy link
Copy Markdown
Owner

@bradygaster bradygaster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PAO review: Sample standardization looks clean. Consistent READMEs and naming. Rebased on dev.

@bradygaster bradygaster merged commit e7b677a into bradygaster:dev Mar 22, 2026
1 of 2 checks passed
chrislomonico pushed a commit to clomonico/squad that referenced this pull request Mar 26, 2026
… (bradygaster#484)

* test: human journey — Power user (bradygaster#396)

Add E2E journey test covering advanced shell features:
- /help and /status slash commands
- Tab completion for /commands and @agent names
- Ctrl+C cancel during processing
- Double Ctrl+C exit
- Multiple slash commands in sequence
- @agent direct routing with complex messages

Closes bradygaster#396

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* test: human journey — I'm waiting and getting anxious (bradygaster#385)

Add E2E journey test covering the user experience while waiting for
agent responses: thinking indicators, phase labels, activity hints,
streaming content updates, /status visibility, Ctrl+C cancellation,
and recovery after cancel.

14 test cases validate the full anxiety-to-reassurance path.

Closes bradygaster#385

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants