{"id":50652958,"url":"https://github.com/steve-piece/bytheslice","last_synced_at":"2026-06-07T22:01:15.177Z","repository":{"id":351405742,"uuid":"1193945054","full_name":"steve-piece/bytheslice","owner":"steve-piece","description":"Plugin for Cursor \u0026 Claude: PRD generation, phased implementation planning, and CI/CD infrastructure hardening","archived":false,"fork":false,"pushed_at":"2026-06-07T11:55:17.000Z","size":763,"stargazers_count":0,"open_issues_count":0,"forks_count":1,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-06-07T13:21:45.086Z","etag":null,"topics":["ai-assisted-development","prd-to-product","skill-md","spec-driven-development","subagents"],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/steve-piece.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":"AGENTS.md","dco":null,"cla":null}},"created_at":"2026-03-27T18:44:58.000Z","updated_at":"2026-06-07T11:55:20.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/steve-piece/bytheslice","commit_stats":null,"previous_names":["steve-piece/phased-dev-workflow","steve-piece/stagecoach","steve-piece/bytheslice"],"tags_count":5,"template":false,"template_full_name":null,"purl":"pkg:github/steve-piece/bytheslice","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/steve-piece%2Fbytheslice","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/steve-piece%2Fbytheslice/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/steve-piece%2Fbytheslice/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/steve-piece%2Fbytheslice/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/steve-piece","download_url":"https://codeload.github.com/steve-piece/bytheslice/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/steve-piece%2Fbytheslice/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":34039495,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-07T02:00:07.652Z","response_time":124,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ai-assisted-development","prd-to-product","skill-md","spec-driven-development","subagents"],"created_at":"2026-06-07T22:01:14.583Z","updated_at":"2026-06-07T22:01:15.164Z","avatar_url":"https://github.com/steve-piece.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003c!-- README.md --\u003e\n\u003c!-- ByTheSlice — npm + GitHub README. Pizza-themed, two-tier: simple-at-top + technical-below. --\u003e\n\n\u003cdiv align=\"center\"\u003e\n\n# 🍕 ByTheSlice\n\n**A grab-and-go pizza shop for shipping software.**\n\n*Plan today's menu. Prep the line. Bake one pie at a time, slide it onto the display tray, and keep service moving until the board is clear.*\n\n[![npm version](https://img.shields.io/npm/v/bytheslice?color=ef4444\u0026label=npm\u0026logo=npm)](https://www.npmjs.com/package/bytheslice)\n[![License: MIT](https://img.shields.io/badge/license-MIT-22c55e.svg)](LICENSE)\n[![Node](https://img.shields.io/node/v/bytheslice?color=3b82f6\u0026logo=node.js\u0026logoColor=white)](https://nodejs.org)\n[![Made for Claude Code](https://img.shields.io/badge/Claude_Code-plugin-orange?logo=anthropic)](https://www.anthropic.com/claude-code)\n[![Made for Cursor](https://img.shields.io/badge/Cursor-plugin-blue?logo=cursor)](https://cursor.com)\n[![GitHub stars](https://img.shields.io/github/stars/steve-piece/bytheslice?style=social)](https://github.com/steve-piece/bytheslice/stargazers)\n\n\u003c/div\u003e\n\n---\n\nByTheSlice runs your project like a **pizza shop**. You don't build a whole app in one prompt — you prep the kitchen, then sell slices to customers one at a time, with quality checks every step of the way. No 200-file PRs nobody reads. No \"what does this even do\" three months later.\n\n**Three steps. Thirteen commands. The kitchen does the rest.**\n\n---\n\n## Table of Contents\n\n**Start here**\n- [How it works — in three steps](#how-it-works--in-three-steps)\n- [Quick Start](#quick-start)\n- [Install](#install)\n\n**Under the hood** *(for developers + power agentic-coding users)*\n- [The Kitchen — workflow diagram](#the-kitchen--workflow-diagram)\n- [The master checklist — Prep + Pies](#the-master-checklist--prep--pies)\n- [Personalize — `bytheslice.config.json`](#personalize--bythesliceconfigjson)\n- [Architecture \u0026 conventions](#architecture--conventions)\n- [Experimental skills](#experimental-skills)\n- [FAQ](#faq)\n- [Contributing](#contributing) · [Repository](#repository) · [License](#license)\n\n---\n\n# Start here\n\n## How it works — in three steps\n\nThink of your project as a pizza shop. There are three things you do, in order. Every command name links to its full reference (`SKILL.md`).\n\n### 🔥 Step 1 — Open the shop *(one-time prep)*\n\nSix things, in order, once per project:\n\n| Command | In pizza terms | What it does |\n|---|---|---|\n| [`/setup-shop`](skills/setup-shop/SKILL.md) | Unlock the doors, fire up the oven. | Bootstraps a new project or drops ByTheSlice into an existing one. |\n| [`/create-menu`](skills/create-menu/SKILL.md) | Decide which pies to serve. | Turns a free-form brief into a structured PRD. |\n| [`/cook-pizzas`](skills/cook-pizzas/SKILL.md) | Pre-bake every pie on the menu. | Decomposes the PRD into Pies (3–8 slices each) + a nested master checklist. |\n| [`/set-display-case`](skills/set-display-case/SKILL.md) | Build the case the pies sit in. | Generates the design system — tokens, components, the `/library` preview route. |\n| [`/final-quality-check`](skills/final-quality-check/SKILL.md) | Install the quality line. | Wires CI/CD, E2E tests, design-system compliance, visual regression. |\n| [`/open-the-shop`](skills/open-the-shop/SKILL.md) | Flip the OPEN sign, stock ingredients. | Sets up env vars + external service credentials. The most hands-on prep step. |\n\n### 🛎️ Step 2 — Serve customers *(the everyday loop)*\n\nWhere you'll spend most of your time. **`/sell-pie`** is the forefront motion — bake a whole Pie autonomously, then box it at the boundary. Reach for **`/sell-slice`** when one slice needs a careful, hands-on touch.\n\n| Command | In pizza terms | What it does |\n|---|---|---|\n| [`/sell-pie`](skills/sell-pie/SKILL.md) | Bake a whole pie, then set the tray on the counter. | **The primary everyday command.** Autonomous baker over one Pie: per-slice build → test → verify → fix, commit + push each slice (no PR), then opens the boundary PR via `/box-it-up`. |\n| [`/sell-slice`](skills/sell-slice/SKILL.md) | Run one slice through the kitchen line by hand. | High-touch single-slice delivery with the library preview gate intact. For sensitive or collaborative work. |\n| [`/box-it-up`](skills/box-it-up/SKILL.md) | Box the pie, ring it up, hand it over. | Opens the `Pie N` PR, watches CI, auto-fixes on red, merges on your approval (never squash), syncs main, cleans up. `--slice` is the per-slice commit+push `/sell-pie` calls. |\n\nA Pie is the unit of autonomy, PR, and context-refresh. **After each Pie merges, start a fresh chat and bake the next one** — until the master checklist is empty.\n\n### ✨ Step 3 — Handle the unusual *(side flows)*\n\nOn-demand, no particular order:\n\n| Command | In pizza terms | What it does |\n|---|---|---|\n| [`/special-order`](skills/special-order/SKILL.md) | Cook something off-menu on the spot. | Bolts new features onto an in-progress project — writes fresh stage files, hands off to `/sell-slice`. |\n| [`/inspect-display`](skills/inspect-display/SKILL.md) | Eyeball every pie on the tray. | Read-only audit of the running app — every route, every page, captured to a report. |\n| [`/run-the-day`](skills/run-the-day/SKILL.md) ⚠️ | Auto-pilot the whole day's service. | Thin chainer that drives `/sell-pie` across every Pie in sequence. *Experimental — fine for short roadmaps, drifts across many pies.* |\n| [`/close-shop`](skills/close-shop/SKILL.md) ⚠️ | Sit down and debrief after service. | Friction retro on the workflow itself — drafts plugin improvements back to disk. *Experimental.* |\n\n\u003e [!IMPORTANT]\n\u003e **Shop rules** the plugin enforces, no exceptions:\n\u003e 1. **Every slice passes the quality line** (lint, type, build + UI test review). A bad pie doesn't go on the display.\n\u003e 2. **Selling and boxing are decoupled.** Slices commit + push to the pie branch with no PR or CI; `/box-it-up` opens the single `Pie N` PR and merges at the **pie boundary** — so CI fires once per pie, and you can taste-test between slices.\n\u003e 3. **Every skill is independently invocable.** Drop `/set-display-case` onto any project to bolt on a design system, or `/box-it-up` onto any branch to push it. The full workflow is opt-in.\n\n---\n\n## Quick Start\n\n```bash\n# 1. Install (one-time)\nnpx bytheslice install --target both\n\n# 2. Open the shop (one-time per project)\n/bytheslice:setup-shop\n/bytheslice:create-menu\n/bytheslice:cook-pizzas\n/bytheslice:set-display-case\n/bytheslice:final-quality-check\n/bytheslice:open-the-shop\n\n# 3. Serve customers (repeat, fresh chat per pie)\n/bytheslice:sell-pie          # bakes a whole Pie autonomously, opens the boundary PR\n# — or, for one careful slice at a time:\n/bytheslice:sell-slice\n/bytheslice:box-it-up\n```\n\nRepeat step 3 until the master checklist is empty. That's the whole motion.\n\n\u003e [!NOTE]\n\u003e Every command also works without the `/bytheslice:` prefix in Claude Code if no other plugin claims it (e.g. just `/sell-slice`). Old v3 names (`/deliver-stage`, `/ship-pr`, etc.) still work for one release as backward-compat aliases.\n\n---\n\n## Install\n\n| Option | Command | When to use |\n|---|---|---|\n| **Claude Code plugin** *(recommended)* | `/add-plugin bytheslice` | Normal interactive use. |\n| **npm CLI** | `npx bytheslice install --target both` | Automation, CI bootstraps, devcontainers. Scriptable + idempotent. |\n| **From GitHub** | `npx github:steve-piece/bytheslice install --target both` | No npm install. |\n| **Pick \u0026 choose skills** | `npx bytheslice install --mode skills --skill setup-shop --skill sell-slice` | Grab individual skills into `./.bytheslice-installs/skills/`. |\n\nDefault install paths — **Cursor:** `~/.cursor/plugins/local/bytheslice` · **Claude Code:** `~/.claude/plugins/bytheslice`. Scope a single host with `--target cursor` / `--target claude`; override paths with `--cursor-dir` / `--claude-dir` / `--skills-dir`. For declarative installs, point `--config \u003cpath\u003e` at a JSONC file (see [`skills-config.example.json`](scripts/install/skills-config.example.json)).\n\n---\n\n# Under the hood\n\n*Everything below is for developers and power agentic-coding users. If you just want to ship features, you can stop at Quick Start.*\n\n## The Kitchen — workflow diagram\n\n```mermaid\nflowchart TD\n    Setup[\"🔥 setup-shop\"] --\u003e Menu[\"📋 create-menu\"]\n    Menu --\u003e Cook[\"🍕 cook-pizzas\"]\n    Cook --\u003e Case[\"🪟 set-display-case\"]\n    Case --\u003e QC[\"✅ final-quality-check\"]\n    QC --\u003e Open[\"🚪 open-the-shop\"]\n    Open ==\u003e Pie[\"🥧 sell-pie\u003cbr/\u003ebake one whole pie\"]\n    Special[\"➕ special-order\"] -.-\u003e Pie\n    Pie -.-\u003e|one careful slice| Sell[\"🛎️ sell-slice\"]\n    Pie ==\u003e Box[\"📦 box-it-up\u003cbr/\u003epie-boundary PR\"]\n    Sell -.-\u003e Box\n    Box ==\u003e Q{\"Pies left\u003cbr/\u003ein the case?\"}\n    Q ==\u003e|Yes, fresh chat| Pie\n    Q --\u003e|No| Inspect[\"🚶 inspect-display\"]\n    Inspect --\u003e Close([\"🌙 close-shop\"])\n\n    classDef prep fill:#dbeafe,stroke:#2563eb,color:#1e3a8a;\n    classDef serve fill:#dcfce7,stroke:#16a34a,color:#14532d;\n    classDef side fill:#f3f4f6,stroke:#9ca3af,color:#374151;\n    classDef done fill:#ede9fe,stroke:#7c3aed,color:#4c1d95;\n\n    class Setup,Menu,Cook,Case,QC,Open prep;\n    class Pie,Sell,Box serve;\n    class Special,Inspect side;\n    class Close done;\n```\n\n🔵 **Prep** *(once per project)* · 🟢 **Service** *(the daily loop)* · ⚪ **Side flows** *(on demand)* · 🟣 **Wrap-up**. Thick arrows are the everyday path; dotted arrows are optional branches.\n\n**Finish a pie, start a fresh chat, bake the next** — until the master checklist is green.\n\n---\n\n## The master checklist — Prep + Pies\n\n`cook-pizzas` produces `docs/plans/00_master_checklist.md` as a **two-level Pie / Slice roadmap** — **Pie 1 — Foundations** (tracked via the `## Prep` gate) then the feature Pies (2+):\n\n```markdown\n## Prep — Pie 1: Foundations (run once before any feature work)\n\n[ ] Display case built       — run /bytheslice:set-display-case\n[ ] Quality line installed   — run /bytheslice:final-quality-check\n[ ] Shop open                — run /bytheslice:open-the-shop\n[ ] DB schema foundation     — run /bytheslice:sell-slice on Slice 1.x (if backend)\n\n## Pie 2 — Blog Editor    \u003c!-- review: boundary --\u003e\n\n### Slice 2.6 — Build the Blog Editor frontend\n[ ] step\n[ ] step\n\n### Slice 2.7 — Wire server actions into the editor\n[ ] step\n```\n\nA **Pie** is a coherent chapter of 3–8 slices; a **Slice** is one vertical deliverable. `/sell-slice`'s prep gate **refuses to start feature work until every Pie-1 / Prep box is `[x]`**. For the full hierarchy, caps, and how legacy flat-v4 / v3 checklists are handled, see [**Architecture \u0026 conventions**](#architecture--conventions).\n\n\u003e [!NOTE]\n\u003e **Hard caps per slice:** 6 tasks, ~10–15 files changed, completable in one fresh agent session. Override `stages.maxTasksPerStage` in `bytheslice.config.json` if you really need a bigger slice — but the cap exists for a reason.\n\n---\n\n## Personalize — `bytheslice.config.json`\n\nDrop a `bytheslice.config.json` at your project root to override defaults:\n\n```jsonc\n{\n  \"modelTiers\":   { \"implementer\": \"opus\", \"qualityReviewer\": \"opus\",\n                    \"sliceTester\": \"sonnet\", \"sliceVerifier\": \"sonnet\" },\n  \"stages\":       { \"maxTasksPerStage\": 6, \"targetFeatureStages\": \"20-30\" },\n  \"verification\": { \"viewports\": [375, 1280],\n                    \"e2e\": { \"feature\": \"always\", \"regressionCore\": \"critical-only\", \"visual\": \"off\" } },\n  \"flow\":         { \"autoApproveBuildPlan\": false, \"libraryGate\": \"self-critique\" },\n  \"review\":       { \"default\": \"boundary\" },   // per-pie override via the `\u003c!-- review: --\u003e` annotation\n  \"mcps\":         { \"shadcn\": true, \"magic\": false, \"figma\": false, \"chromeDevTools\": true },\n  \"visualReview\": { \"tools\": [\"claude-in-chrome\", \"chrome-devtools-mcp\", \"playwright\"], \"vizzly\": false },\n  \"hitl\":         { \"additionalCategories\": [] },\n  \"rules\":        { \"imports\": [] },\n  \"runPipeline\":  { \"platformWalkEvery\": 5, \"haltOn\": \"broken\" }\n}\n```\n\n**Precedence (top wins):** `env vars` → `bytheslice.config.json` → `project rules file (CLAUDE.md / AGENTS.md)` → `plugin defaults`.\n\nFull schema and precedence rules: [`bytheslice-config-schema.md`](skills/setup-shop/references/bytheslice-config-schema.md). System-wide defaults live at `~/.bytheslice/defaults.json` (created during first-time install). Config keys keep their v3 names for backward compatibility; as of v5 the `ciCdGuardrails` / `basicChecksRunner` / `aggregatingTestReviewer` tiers are deprecated aliases of `sliceVerifier` and still resolve.\n\n---\n\n## Architecture \u0026 conventions\n\nThe kitchen runs on a handful of non-negotiable rules — per-slice **verify-once**, **context-separated** dispatch, **preview-first** library delivery, **deterministic hook** enforcement. The full reference lives in **[docs/architecture.md](docs/architecture.md)**:\n\n- [**Pies \u0026 Slices**](docs/architecture.md#pies--slices--the-two-level-checklist) — the two-level checklist, caps, the Prep gate\n- [**Mode detection**](docs/architecture.md#mode-detection--standalone-vs-sequential) — standalone vs sequential, per-skill posture table\n- [**The verify-once model**](docs/architecture.md#the-verify-once-model) — tester + verifier, build manifest, context separation, type-routed testing\n- [**Delivery \u0026 git**](docs/architecture.md#delivery--git--selling-vs-boxing) — selling vs boxing, one pie per PR, worktrees\n- [**Design-system delivery**](docs/architecture.md#design-system-delivery) — preview-first library gate, visual review tooling\n- [**Orchestration principles**](docs/architecture.md#orchestration-principles) — subagent-driven, exit-criteria contract, HITL bubbling, model tiers\n- [**Hook enforcement**](docs/architecture.md#hook-enforcement) — what the [`hooks/`](hooks/) layer blocks at the tool level\n- [**Legacy \u0026 migration**](docs/architecture.md#legacy--migration) — flat v4 / v3 projects, `--repie`\n\n---\n\n## Experimental skills\n\n\u003e [!WARNING]\n\u003e Not currently reliable in Claude Code or Cursor — agent attention drifts on long-running multi-stage tasks. Curious how they hold up in systems with stronger long-horizon multi-agent orchestration.\n\n`/sell-pie` (one Pie per run, stopping at the boundary) is the autonomous surface and is **not** experimental. The experimental part is unattended *whole-roadmap* automation:\n\n- **`/run-the-day`** — thin chainer that drives `/sell-pie` across **every** Pie until the checklist is green.\n- **`/close-shop`** — after-service retrospective that drafts plugin improvements back to disk.\n\nRunning in **Cursor or any host without `/loop`, `Workflow`, or `/goal`?** The skills don't silently drop the logic — they fall back to in-context self-pacing with manual schema validation. See the [Cursor / non-Claude-Code fallback](docs/architecture.md#cursor--non-claude-code-fallback) section.\n\n---\n\n## FAQ\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eDo I need both Claude Code and Cursor?\u003c/b\u003e\u003c/summary\u003e\n\nNo. ByTheSlice works in either host on its own. `--target both` is just a convenience for people who jump between IDEs.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWhat's the smallest possible slice?\u003c/b\u003e\u003c/summary\u003e\n\nA slice has to be a real *user-facing* delta — UI + route + data + tests for one thing. The hard floor is roughly \"one button that actually does something end-to-end.\" If you can't draw a user-visible bite out of it, it belongs as part of a foundation prep step instead.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eCan I skip the verification gates?\u003c/b\u003e\u003c/summary\u003e\n\nTechnically yes (the orchestrator will accept a HITL override with `destructive_operation` category), but every story we've seen of \"I'll just skip the gates this once\" ends with a slice that breaks main. The whole point is that the kitchen doesn't ship slices it didn't taste.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWhat happens if a slice is too big?\u003c/b\u003e\u003c/summary\u003e\n\n`/sell-slice` will stop at the 6-task / ~15-file cap and return `needs_human: true` with category `prd_ambiguity` asking you to split the stage. Then re-run `/cook-pizzas` against the same PRD with that stage flagged for further decomposition (or use `/special-order` to add a refined split).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eDoes this work with non-Next.js stacks?\u003c/b\u003e\u003c/summary\u003e\n\nYes. As of v4.2, `/setup-shop` bootstraps **Next.js (App Router or Pages), Vite + React, SvelteKit, and Astro** directly, plus a plain **Node API** flow with no frontend. The canonical support matrix lives in [`framework-detect.md`](skills/setup-shop/references/framework-detect.md).\n\nNext.js App Router is the most-validated path end-to-end. The other frontends bootstrap and get a full design system + CI/CD scaffold, but the Phase 4.5 library-preview templates currently assume App Router conventions — non-Next stacks bubble a one-time HITL at that gate until per-framework templates land. The verification gates and skill orchestration are stack-agnostic regardless. Remix and Nuxt are not yet detected; they bubble HITL and stop.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eI just want to add a design system / CI/CD / env-setup to my existing app. Do I have to do the full workflow?\u003c/b\u003e\u003c/summary\u003e\n\nNo. Every foundation skill is standalone-invocable. Drop into any project and run just `/bytheslice:set-display-case` (or `/final-quality-check`, or `/open-the-shop`). They auto-detect that there's no master checklist and run end-to-end without trying to coordinate with one.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eHow do I uninstall?\u003c/b\u003e\u003c/summary\u003e\n\n```bash\nrm -rf ~/.cursor/plugins/local/bytheslice ~/.claude/plugins/bytheslice\n```\n\nThat's it. The plugin doesn't write anywhere else outside your project's `bytheslice.config.json`.\n\n\u003c/details\u003e\n\n---\n\n## Contributing\n\nContributions are welcome — especially if you've got real-world friction reports from running long plans.\n\n```bash\n# 1. Fork + clone, then install your fork locally for live testing\ngit clone https://github.com/\u003cyour-username\u003e/bytheslice.git\ncd bytheslice\nnode ./bin/bytheslice.js install --target both\n\n# 2. Make your slice on a branch, then push and open a PR\ngit checkout -b feat/\u003cscope\u003e\ngit commit -m \"feat: \u003cwhat changed\u003e\"\ngit push -u origin HEAD\n```\n\nThe plugin eats its own cooking — internal changes go through the same `/sell-slice` → `/box-it-up` motion. Run `/bytheslice:close-shop` after a release to surface friction and draft improvements back to the repo.\n\n---\n\n## Repository\n\n- **GitHub:** [steve-piece/bytheslice](https://github.com/steve-piece/bytheslice)\n- **npm:** [bytheslice](https://www.npmjs.com/package/bytheslice)\n- **Changelog:** [CHANGELOG.md](CHANGELOG.md) · **Architecture:** [docs/architecture.md](docs/architecture.md) · **Issues:** [GitHub Issues](https://github.com/steve-piece/bytheslice/issues)\n\n---\n\n## License\n\n[MIT](LICENSE) © Steven Light\n\n\u003cdiv align=\"center\"\u003e\n\n—\n\n*Open the shop. Sell one slice at a time. Taste-test before it leaves the kitchen.*\n\n🍕\n\n\u003c/div\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsteve-piece%2Fbytheslice","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsteve-piece%2Fbytheslice","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsteve-piece%2Fbytheslice/lists"}