claude

tsf

Toby Software Factory: an agentic software factory over a GitHub-issue backlog — one work step per cycle in a fresh context, async human gates on the issue, artifacts in the repo, and approved work landed unattended.

1 on GitHubby Tobias Schlittv1.3.0updated 8 days ago
/

Plugin tsf from marketplace toby-plugins in tobyS/toby-plugins. Commands read from the repo's manifest — 8 days ago.

What it installs

Slash commands (3)

  • /tsf:cycle

    Run one factory cycle — scan the tsf:* backlog over REST, pick the highest-priority actionable ticket, advance it exactly one step in a fresh agent context, and perform every GitHub write. Re-invoke it with /loop /tsf:cycle.

  • /tsf:init

    Set up tsf in this project — analyze it, agree the GitHub coordinates, factory identity, responders and environment contract, write .claude/tsf/config.md, create the tsf:* labels, check the factory credential, and offer the allowlist and the comment-pickup workflow.

  • /tsf:spec

    Author a factory spec through guided discussion, then create the ticket triple — GitHub issue, ticket branch and thoughts/factory/GH-<n>/spec.md — over REST under your own login, and offer to release it with tsf:queued.

Subagents (12)

  • dossier

    Internal to `/tsf:cycle` — not for direct use. Writes the review dossier from everything on the ticket branch — narrative, curated permalinks, open items, overlapping pull requests — keeps the pull request's title and body in line with their template, and writes the landing-refusal addendum. Returns

  • implement

    Internal to `/tsf:cycle` — not for direct use. Implements an approved plan increment by increment, running each increment's own verification and committing it; also addresses a review (rework) and fixes what gate reports evidence (fix). Returns a result block.

  • integration

    Internal to `/tsf:cycle` — not for direct use. Judges whether an approved pull request and the changes the base branch took since its approval can break each other in ways the tests would not catch. Receives only the two diff paths and the spec text.

  • manual-verify

    Internal to `/tsf:cycle` — not for direct use. Attempts every plan item flagged Manual with real checks — project commands, throwaway scripts, MCP servers — and reports per-item evidence, escalating only what genuinely needs a person. Returns a result block.

  • merge-resolver

    Internal to `/tsf:cycle` — not for direct use. Resolves a conflict between an approved pull request branch and the base branch in the factory's clone, classifying the resolution mechanical or logic. Returns a result block.

  • plan-compliance

    Internal to `/tsf:cycle` — not for direct use. Judges a pull request diff against the plan's per-increment verification criteria, from a fresh context, returning one evidenced verdict per criterion — nothing else. Receives only the criteria and the diff path.

  • plan

    Internal to `/tsf:cycle` — not for direct use. Writes a ticket's plan.md as independently verifiable increments from spec and research and summarizes it for approval; on resume classifies the responder's reply as approval or feedback and revises. Returns a result block.

  • research

    Internal to `/tsf:cycle` — not for direct use. Researches the codebase for a ticket's spec and writes research.md with file:line evidence, asking only questions that materially affect planning; on resume folds the answers into spec.md and re-validates. Returns a result block.

  • security

    Internal to `/tsf:cycle` — not for direct use. Reviews a pull request diff for security defects, classifying each finding blocking or advisory with evidence. Receives only the diff path and may read the touched files' surroundings; never any thoughts/ document.

  • spec-coverage

    Internal to `/tsf:cycle` — not for direct use. Judges a pull request diff against the ticket's spec alone — never the plan — returning one evidenced verdict per spec requirement. This is the spec-drift catcher. Receives only the spec text and the diff path.

  • triage

    Internal to `/tsf:cycle` — not for direct use. Distills a raw GitHub issue into the ticket's spec.md, tests it for sufficiency, and folds a responder's answers into it on resume. Returns a result block.

  • verify-fix

    Internal to `/tsf:cycle` — not for direct use. Makes a red verification green — the project's suite locally, or CI on the pull request head — diagnosing by local reproduction first and committing the fix. Returns a result block.

View source on GitHub

More from tobyS/toby-plugins

All 4 plugins →

tce

claude

Context-engineering workflow: ticket → intent → research → plan → implement, plus review/discuss/design commands and research agents. Agrees intents (/tce:intent) and works with any ticket system (tmt, GitHub, Jira, Linear, …).

14 commands · 13 agents · hooks

1

tle

claude

Toby Loop Engineering: an autonomous convergence loop — define a machine-checkable goal, then iterate verify → spec → implement until every checklist item verifiably passes. Greenfield-first; file-only handoffs under thoughts/shared/loops/.

2 commands · 4 agents

1

tmt

claude

Toby Markdown Tickets: lightweight Git-tracked ticket tracker — tickets as markdown files in your repo, owning the envelope (sequential numbering, status-lifecycle hooks, create/update). tce's native ticket backend.

4 commands · hooks

1

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

superpowers

claudecodex

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

15 skills · hooks

obra/superpowers 316,836

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Maintain tsf?

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 plugins4 plugins