AISWEC
AI SOFTWARE ENGINEERING CORE
YOU AISWEC[BOT]

Task in. Build out.

AISWEC is development automation for GitHub. Write the task in Suite, in plain words. It answers with a plan; you approve it; it builds behind your own CI gates and answers your review with commits.

Open Suite See the pipeline ↓
ISSUE #214 facts-game
Implement EAS Workflows
aiswec[bot] · plan · approved by you
eas.json · build.yml · submit on tag
opened by you · aiswec refined
  1. REFINE
  2. APPROVE
  3. BUILD
  4. REVISE
  5. MERGE
refined → ready-to-build → pr-open
PULL REQUEST #87 (MERGED) gates ✓ 3/3
aiswec/issue-214-implement-eas-workflows
◌ actions/build · queued● actions/build · running✓ actions/build · 38s
◌ actions/deploy · queued● actions/deploy · running✓ actions/deploy · live
opened by aiswec[bot] · waiting on your reviewapproved by you
  1. TASK IN → BUILD OUT
  2. MAINTAIN YOUR REPOS ON THE GO
  3. KEEP DEVELOPMENT MOVING
  4. PUT YOUR CLAUDE SUBSCRIPTION TO WORK
  5. SECURE AND TRANSPARENT, ALL ON GITHUB
  6. YOUR SECRETS NEVER LEAVE GITHUB

You write product. It writes software.

Four steps on one repository, in two lanes: the white lane is you, the blue lane runs unattended on your own GitHub Actions. Your only verbs are write, approve, review and merge. Every hand-off is a GitHub resource you can read, a comment, a label, a pull request; never a hidden state.

YOUR LANE AISWEC'S LANE
  1. Write the task

    A title is enough. Label the issue aiswec, or file it as a task from Suite.

    you · one line
  2. Refine

    Reads the repository with read-only tools and posts the plan on the thread: scope, files, tests. Nothing is built yet.

    sonnet · 40 turns · aiswec:refined
  3. Approve the plan

    The first line of a comment: approve, lgtm, ship it. Anything else is feedback, and re-refines.

    you · one comment · zero tokens
  4. Build

    A branch, commits and a pull request on aiswec/issue-N, behind your own CI gates, three tries. Red gates leave a draft WIP PR flagged for you, never a quiet failure.

    opus · 120 turns · aiswec:pr-open
  5. Review

    Review it like anyone's: inline comments, review bodies, plain replies. All of it counts.

    you · as many rounds as you like
  6. Revise

    Every thread answered with replies and commits on the same pull request, until you merge.

    opus · 120 turns · until you merge
  7. Merge

    Yours, always. Nothing merges itself; your own Actions build and ship it.

    you · merge · shipped

Scroll the diagram sideways to follow both lanes.

Refine
sonnet, 40 turns, 15 minutes. Read-only tools; the plan is posted on the issue, where you can read it.
Build and revise
opus, 120 turns, 40 minutes each, behind your own CI gates with three tries. Red gates leave a draft WIP PR for you.
You
Write, approve, review, merge. One comment approves, and approval costs zero tokens.
The brakes
aiswec:hold stops an issue in any state, even an approved one. aiswec:needs-human asks for you; any maintainer comment revives the stage.
SUITE · THE CLIENT FOR THE PIPELINE

File an issue tonight. Review a pull request with coffee.

Suite is the web app on top of the pipeline: projects, the board, approvals, reviews, runs. Sign in with GitHub and install on a repository. Set up is one button that writes the stages, labels and secrets. Remove is one button too.

Open Suite github is the database · your token, your repo