making-things

Files (12)

• SKILL.md
• openai.yaml · agents/
• execution-modes.md · references/
• handoff-protocol.md · references/
• sidecar-control-repository.md · references/
• workstream-protocol.md · references/
• CAPABILITY-SMOKE.md · templates/
• CONTRACT.md · templates/
• HANDOFF.md · templates/
• PROJECT.md · templates/
• TASK.md · templates/
• TRACK.md · templates/

SKILL.md (first lines)

# Making Things

Coordinate an Electron workflow whose durable records live in a sibling Git
control repository, not in the code repository or chat history.

## Start or resume

1. Require explicit user invocation. Do not auto-start a workflow.
2. Discover `../.making/<project-slug>/PROJECT.md` from the code repository.
   If it is absent, explain the sidecar setup required by the packaged
   `PROJECT.md` template; do not create a repository, branch, worktree,
   commit, or push automatically.
3. Read `PROJECT.md`, the relevant workstream `TRACK.md`, its unfinished
   `TASK.md` records, and `HANDOFF.md` when present.
4. Confirm the current lane, lowercase date-summary, branch, and relative
   worktree agree with the records. The parent Agent is responsible for
   manually creating and entering the declared Git worktree.
5. Route to `product-prd`, `solution-architecture`, `mts-split`, `mts-one`,
   `mts-more`, `handoff`, `handon`, or the Electron specialist Skill that
   matches the requested work. Do not infer authority from a host brand.
6. Update only the appropriate sidecar Markdown record with decisions,
   evidence, review, result, or handoff information. Never persist secrets,
   raw prompts, or absolute machine paths.

## Non-negotiable rules

- Workstream classes are only frontend, backend, and integration. A contract
  must make frontend and backend scopes disjoint before parallel work begins.
- TDD subtasks do not receive separate Git branches or worktrees.
- `mts-one` is the universal parent-led mode. `mts-more` may dispatch one
  writing native subagent at a time only with dated `WRITE_SUBAGENT:
  VERIFIED` evidence for the current host; otherwise report `DEGRADED` and
  use `mts-one`.
- Handoff pauses and resumes a complete workstream only. Optional hooks are
  informational and never enforce correctness or mutate task records.
- All native capability statements must be `VERIFIED`, `DEGRADED`, or
  `UNSUPPORTED`; a verified statement requires dated smoke evidence.
- Preserve Electron process boundaries, validate IPC input and sender, use
  test-first development for behavior changes, and obtain explicit user
  authorization before any delivery action.

## Sidecar protocol

Use `references/sidecar-control-repository.md` for the repository boundary
and `references/workstream-protocol.md` for names, collision handling, and
state definitions. Use the packaged templates when creating sidecar records:

- `PROJECT.md` establishes a project control repository.
- `CONTRACT.md` is approved before frontend/backend parallelism or splitting.
- `TRACK.md` represents one shared frontend, backend, or integration code
  worktree.
- `TASK.md` represents one TDD-sized work item within that track.
- `HANDOFF.md` pauses and transfers a workstream only.
- `CAPABILITY-SMOKE.md` records actual native-host observations.

When a user asks to derive workstreams from an approved contract, invoke
`mts-split`. Do not replace its collision check with host-specific authority
rules or automatic Git actions.

From SuShuheng/making-things, MIT.

More from SuShuheng/making-things