claude

pyhouse-delivery

How one change is delivered, rather than how its code is written. Ships the delivery-spec skill — the spec a change is implemented from, short enough to review in one sitting, naming as contracts only what other code depends on and stating the behaviour its tests are written from, its statements about today's system checked before any code exists, and its goal, scope and contracts frozen once it is ready. And /pyhouse-delivery:spec, which writes that spec with the person who wants the change, checks those statements and marks the spec ready once the person has accepted it. Ships delivery-change-contract — the short list of what is frozen while a ready spec is implemented, and every edit to it caught by a diff from a base commit rather than forbidden. And /pyhouse-delivery:implement, which implements a ready spec through the delivery-implementer subagent, which writes the tests from the spec before the code, then the code, and checks its own work by the project's gate and, where the change shows only in a running process, a live check — then /pyhouse-universal:change-review and one round of fixes — and hands over the body of the merge commit. Depends on pyhouse-universal.

3 on GitHubby Yegor Vorobyevv0.5.0MITupdated 2 days ago
/

Plugin pyhouse-delivery from marketplace pyhouse in wntic/pyhouse. Commands read from the repo's manifest — 2 days ago.

What it installs

Skills (2)

  • delivery-change-contract

    Use when implementing a ready spec and about to change something other than the change's own code — a test written before the code, a test that existed before the change, a gap the spec left, the spec's goal or scope, a decision record, or a check that guards the repository such as the architecture

  • delivery-spec

    Use when writing, splitting or checking the spec for one change before it is implemented — a feature or a fix, what it names as contracts, and the behaviour its tests are written from. Owns the spec's sections and which of them exist only where the project has them, the shorter form a fix takes, con

Slash commands (2)

  • /pyhouse-delivery:implement

    Implement one ready spec end to end — an implementer that writes the tests from the spec before the code, then the code, and checks its own work by the project's gate and, where the change shows only in a running process, a live check; a review of what the change breaks; and one round of fixes — and

  • /pyhouse-delivery:spec

    Write the spec for one change with the person who wants it — the questions, the file, and every statement it makes about today's system checked before any code exists — and mark it ready only once the person has accepted it and each check has passed

Subagents (1)

  • delivery-implementer

    Implements one ready spec in its repository and checks its own work, in the step its caller names — build, which writes the tests from the spec before the code and then the code, or for a fix the regression test seen failing on today's code and then the fix, then runs the project's full gate and, wh

View source on GitHub

More from wntic/pyhouse

All 6 plugins →

Python house-style rules that bind whichever architecture a service uses: naming derivation, typing and logging forms, the package and re-export contract, settings read from the environment, the data-access obligations every store meets, what a program owes a unit delivered at least once, the lint, type-check and dependency configuration every distribution carries once, the single error catalogue, what a distribution's version promises and which change moves it, the testing constitution, the workspace root for a repository holding several distributions, the container image a runnable program ships in, and a command-line interface's commands, exit codes and their test. Ships the hex-vs-flat architecture chooser and its /choose-architecture command, so a greenfield service can settle its family before installing pyhouse-hex or pyhouse-flat, the /pyhouse-universal:adopt command, which tells a repository's agents which skill governs each kind of Python work, and the namespaced /pyhouse-universal:code-review command with the reviewer subagent behind it, which applies these skills to existing code instead of writing new code, and the /pyhouse-universal:change-review command with the change-reviewer subagent behind it, which reviews a change before it lands for the contracts it breaks, the failure paths nothing catches and the tests that would not notice, each finding with the scenario that goes wrong.

18 skills · 4 commands · 2 agents

3

Hexagonal (ports-and-adapters) Python service skills: layer boundaries and the composition root, entities and value objects, repository and capability ports, CQRS commands, queries and handlers, relational persistence with paired migrations, dishka wiring, the FastAPI REST family with optional token auth, and the eight test families that cover them. Depends on pyhouse-universal, which Claude Code installs with it.

23 skills

3

Flat package-by-technical-role Python service skills for workers, crawlers, pipelines, ETL and glue, written for one distribution on its own and equally true of one among several: the one-time project setup — the dependencies each role brings and the migration bootstrap — the four role kinds and the import contract between them, one data-access package per store, named for its technology and the obligations that come with it, entrypoint trigger choice between loop, schedule, stream, HTTP and durable execution, and the four test families that cover them. Depends on pyhouse-universal, which Claude Code installs with it.

8 skills

3

Repository workflow, independent of language and of any architecture. Ships the git-commit-message skill, which carries the Conventional Commits 1.0.0 convention an agent follows whenever it writes a commit message — a type that records the release the change earns, feat for a minor, fix for a patch, a break for a major, or for a minor below 1.0.0, so a version is read off the history instead of argued at release time. Also the git-branching skill — one mainline, one merge method recorded per repository, short-lived branches whose history is cleaned before it lands and never rewritten after. Then /pyhouse-git:adopt, which records in a repository's agent instructions how its changes branch, land and are committed and turns off the agent's own authorship line, /commit, which stages the named files, reviews the staged diff and commits only those files by git-commit-message, and /install-commit-hook, which puts a commit-msg hook in the repository so a malformed message is refused at commit time, and /release, which proposes the next version from the commit types since the last tag and cuts it only on an explicit yes. And /release-notes, which drafts the release note for the project's users from the changes themselves, never from the commit subjects. Depends on nothing and is installed on its own.

2 skills · 5 commands

3

pyhouse

claude

The whole pyhouse catalogue in one install: depends on pyhouse-universal, pyhouse-hex, pyhouse-flat, pyhouse-git and pyhouse-delivery, which Claude Code installs with it, and ships /pyhouse:setup, which sets a repository up for them in one run — the Python skill table and the branching section in its CLAUDE.md, the agent's authorship line turned off, and the commit-msg hook — by running each plugin's own commands in turn. Holds no skill and states no rule of its own.

1 command

3

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows

18 skills

MiniMax-AI/skills 13,828

worktrunk

claudecodex

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.

2 skills · hooks

max-sixty/worktrunk 12,481

gsd-core

claude

GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.

72 skills · 72 commands · 64 agents · hooks

open-gsd/gsd-core 11,494

Maintain pyhouse-delivery?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins6 plugins