Skip to content

Headless Factory skills for the Architecture review #229

Closed

Description

@JacobStephens2

Parent

#27

What to build

Add headless Factory skills for the Architecture review: copies of improve-codebase-architecture, to-spec, to-tickets and codebase-design in the factory's skills, kept close to the interactive originals so they can be re-synced. They're embedded in the binary and loaded as thirdshift: plugin skills (ADR-0001), and they refer to each other by that namespace.

Every human step is replaced:

  • The HTML report becomes Markdown with Mermaid before/after diagrams, written into the issue.
  • The review takes the top recommendation instead of asking, and implements it only when it is Strong.
  • The grilling loop becomes the agent settling the design tree itself, recording each decision and its reason in the plan.
  • to-spec publishes without checking seams with a user.

The skills write nothing to the repository: any CONTEXT.md or ADR change goes into a Ticket as work. They skip any candidate already covered by an open issue. A Strong top recommendation is published as the plan, labelled needs-triage: a Spec with Tickets (with GitHub "blocked by" links, Tickets labelled ready-for-agent), or a single Ticket when one session is enough. Otherwise the top recommendation is filed as one needs-triage idea issue, unless an open issue already covers it. The review ends with one fixed-format final line naming the plan, the idea issue, or the open issue that already covers the idea.

Acceptance criteria

  • The four headless skills are in the factory's skills and load as thirdshift: plugin skills (the existing packaging and plugin tests pass and cover them).
  • No skill opens a browser, asks a question, waits for a user, or writes to the repository.
  • Only a Strong top recommendation becomes a plan; the plan's top issue is labelled needs-triage, and its Tickets ready-for-agent with blocking links.
  • A change that fits one session becomes a single Ticket, not a Spec.
  • Without a Strong candidate, one needs-triage idea issue is filed, or none if an open issue already covers it.
  • Candidates that weren't chosen are dropped, not filed.
  • The final-line format is defined in one place and matches what the Session prompt asks for.
  • The interactive skills in .claude/skills/ are unchanged.

Blocked by

None (can start immediately)

Activity

  1. JacobStephens2 commented on Oct 1, 2026

    @JacobStephens2
    OwnerAuthor

    Closed by #238, merged into issue-27 by a thirdshift Merge run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified, ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions