Development · By owainlewis

Use Machinist to create, assign, and monitor software tasks.

owainlewis/machinist

Lets one Codex thread run a batch of GitHub issues through separate worker threads, each with its own worktree, branch, tested pull request and gated merge.

owainlewis/blueprint

Review code changes for bugs, security issues, performance problems, and style violations.

owainlewis/youtube-tutorials

Has a separate agent review a code change without editing it, checking behavior, security, regressions, complexity, tests and docs before merge.

owainlewis/blueprint

Designs and maintains root ARCHITECTURE.md for the intended system, including its data model and shared technical rules.

owainlewis/blueprint

Reviews a technical proposal before implementation through an independent subagent, returning findings, open questions and a verdict without rewriting it.

owainlewis/blueprint

Creates or updates a long-running REQUIREMENTS.md that defines a system's users, outcomes, capabilities, business rules, scope and acceptance conditions.

owainlewis/blueprint

Writes one implementation-ready spec for a feature or major change, settling behavior, technical design, failure handling and acceptance checks before delivery.

owainlewis/blueprint

Makes existing code easier to understand without changing behavior.

owainlewis/blueprint

Delivers specs or decided tasks as tested, independently reviewed pull requests.

owainlewis/blueprint

Delivers a spec or decided task through the task-to-pr workflow and merges after all quality and approval gates pass.

owainlewis/blueprint