| name | mts-split |
| description | Use when an approved Electron contract must split one feature into frontend, backend, and integration workstreams with TDD task records. |
MTS Split
Turn an approved Electron contract into three coordinated, Git-backed
Markdown workstreams. This Skill writes or directs the parent Agent to write
sidecar records only; it never runs Git operations.
Preconditions
- Require an explicit user request to split the feature.
- Read the sidecar
PROJECT.md and an approved CONTRACT.md.
- Reject the split if the contract does not define renderer ownership,
main/preload/IPC ownership, errors, permissions, and cross-track acceptance.
- Choose a lowercase
YYYY-MM-DD-english-summary. Reject another form.
- Inspect active sidecar tracks and tasks. Reject any cross-lane scope
overlap unless an explicit dependency serializes the work.
Create records
Using the packaged templates, create exactly these tracks under the sidecar:
workstreams/
frontend/<date-summary>/TRACK.md
backend/<date-summary>/TRACK.md
integration/<date-summary>/TRACK.md
For each track record:
- Set
branch to {lane}/{date-summary}.
- Set
worktree to .worktrees/{lane}/{date-summary}.
- Set
status: NOT_STARTED, an initial current_task, and an execution mode.
- State the owned paths and excluded paths. Do not create a code worktree or
branch; the responsible parent Agent does that manually before activation.
Create one or more TDD task records under
work-items/{frontend|backend|integration}/<work-item-id>/TASK.md.
- Each task declares dependencies, scope, deliverables, and execution mode.
- Frontend owns renderer work; backend owns main/preload/IPC work; integration
owns cross-track E2E and assembly work.
- Integration tasks depend on the specific declared frontend and backend
deliverables. Do not mark integration ready before they are complete.
- A task must not declare a Git branch or worktree.
Report and stop
Report the three track locations, task IDs, scope boundaries, dependencies,
and the manual action each parent Agent must take to create/enter its declared
worktree. Do not claim parallel safety without the recorded disjoint scopes.
Do not start implementation; route the chosen task to mts-one or mts-more.
