implement-from-stub

Stars11

Forks2

UpdatedJuly 7, 2026 at 08:33

Write the minimum production code to turn the target's tests green, implementing the .py from its fixed .pyi.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

nullhack

nullhack/temple8

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	implement-from-stub
description	Write the minimum production code to turn the target's tests green, implementing the .py from its fixed .pyi.

Implement From Stub

Load [[software-craft/source-stubs]], [[software-craft/tdd]], [[software-craft/design-patterns]] — stub sync, the cycle, and implementation patterns.
Implement — or, for rework, re-implement — the .py from its .pyi. The .pyi signature is the spec; fill or correct the body to satisfy it and pass the tests. Keep the .py consistent with its sibling .pyi.
Emit the structural artifacts the module requires, keyed on what it is: IF an ORM model THEN emit an Alembic migration (the migration is the schema spec); IF an external adapter THEN reproduce the recorded request shape exactly (method, path, query parameters, headers from external-contracts.md) — vcr matches the request strictly, so the implementation conforms to the cassette, not the other way around. Config follows 12-factor per [[software-craft/secrets-and-config]]: non-secret config via load_dotenv() from the workspace .env; secrets via dotenv_values() from ~/.secrets/<project>.env — read once into a frozen typed Settings, never into os.environ. IF an auth-dependent test fails on credentials THEN stop and ask the user with suggestions — do not investigate the secret.
IF the body cannot satisfy the .pyi without changing it THEN that is a contract gap — do not edit the stub; escalate at review.
Run stubtest scoped to the modules built this cycle — the source module(s) and the test module(s) whose pending marks were removed. The whole-suite stubtest waits until every source .py exists, because unbuilt sibling stubs would false-fail per [[software-craft/source-stubs]], [[software-craft/tdd]].
Stubtest imports the runtime module, so every transitive runtime dependency must be installed in the project venv. IF an import is used only for types THEN prefer if typing.TYPE_CHECKING: so stubtest does not pull heavy runtime deps for type-only references.

More from this repository

same repository

simulate-contracts

nullhack/temple8

Compile the contract set in your head — simulate how the real application would run from the specs, and disprove (or confirm) it works before any source .py is written.

2026-07-0811

author-test-stubs

nullhack/temple8

Author test stub files (.pyi) whose signatures express the domain, relationships, and compositions, as the first contract surface.

2026-07-0811

interview-building-blocks

nullhack/temple8

Funnel level 3 — identify building-block names and rough boundaries only, and run gap analysis.

2026-07-0811

interview-general

nullhack/temple8

Funnel level 1 — establish the big picture with seven broad questions, applying CIT, Laddering, and CI Perspective throughout.

2026-07-0811

merge-to-dev

nullhack/temple8

Squash-merge the feature commits into dev, regenerate docstrings, and verify the whole suite plus whole-suite stubtest are clean.

2026-07-0811

publish-release

nullhack/temple8

Publish the delivered batch as release notes, a PR to main, or a tagged release.

2026-07-0811

Implement From Stub

Load [[software-craft/source-stubs]], [[software-craft/tdd]], [[software-craft/design-patterns]] — stub sync, the cycle, and implementation patterns.

Implement — or, for rework, re-implement — the .py from its .pyi. The .pyi signature is the spec; fill or correct the body to satisfy it and pass the tests. Keep the .py consistent with its sibling .pyi.

Emit the structural artifacts the module requires, keyed on what it is: IF an ORM model THEN emit an Alembic migration (the migration is the schema spec); IF an external adapter THEN reproduce the recorded request shape exactly (method, path, query parameters, headers from external-contracts.md) — vcr matches the request strictly, so the implementation conforms to the cassette, not the other way around. Config follows 12-factor per [[software-craft/secrets-and-config]]: non-secret config via load_dotenv() from the workspace .env; secrets via dotenv_values() from ~/.secrets/<project>.env — read once into a frozen typed Settings, never into os.environ. IF an auth-dependent test fails on credentials THEN stop and ask the user with suggestions — do not investigate the secret.

IF the body cannot satisfy the .pyi without changing it THEN that is a contract gap — do not edit the stub; escalate at review.

Run stubtest scoped to the modules built this cycle — the source module(s) and the test module(s) whose pending marks were removed. The whole-suite stubtest waits until every source .py exists, because unbuilt sibling stubs would false-fail per [[software-craft/source-stubs]], [[software-craft/tdd]].

Stubtest imports the runtime module, so every transitive runtime dependency must be installed in the project venv. IF an import is used only for types THEN prefer if typing.TYPE_CHECKING: so stubtest does not pull heavy runtime deps for type-only references.