메뉴
Local TODO.md backend operations for the microfactory — find eligible items, claim, comment, and transition by editing checkbox states in a markdown file. Used by plan-next and implement-next when the configured backend is todo. Good for trying out the factory without Jira or GitHub.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | todo-tasks |
| description | Local TODO.md backend operations for the microfactory — find eligible items, claim, comment, and transition by editing checkbox states in a markdown file. Used by plan-next and implement-next when the configured backend is todo. Good for trying out the factory without Jira or GitHub. |
Tasks live in a local markdown file (the project path in .microfactory/config.yaml). No authentication, no CLI — operations are file edits. The issue key is TODO-<line-number> (1-based line number of the item in the file).
One item per line, a checkbox list. The checkbox character encodes the status; labels are inline [tag] markers in the text:
- [ ] Add a health check endpoint
- [ ] Rework the auth flow [needs-plan]
- [>] Fix the flaky integration test
- [x] Update the README
- Note: Implemented: Update the README
| Checkbox | Status |
|---|---|
[ ] | Open (claimable) |
[>] | In Progress / In Review |
[~] | Planning |
[?] | Awaiting Plan Review |
[p] | Plan Approved (claimable for implementation) |
[x] | Done |
By mode and the plan_by_default setting:
| Mode | plan_by_default | Eligible lines |
|---|---|---|
| planning | true | [ ] without a [skip-plan] tag |
| planning | false | [ ] with a [needs-plan] tag |
| implementation | true | [p], or [ ] with a [skip-plan] or [plan-approved] tag |
| implementation | false | [ ] without a [needs-plan] tag |
TODO-<n>.[~] (planning mode) or [>] (implementation mode).This backend is single-user, so no race verification is needed.
<n> of the file. - Note: <text>[>]; Done is [x]). A human reviewer approves a plan by changing [?] to [p].Commit changes to the TODO file together with the related work so the backlog history stays in git.
Run one planning iteration of the microfactory — claim the next planning-eligible issue from the configured backend, explore the codebase, write plans/<KEY>.md, push it, and put the issue up for plan review. Intended as a /loop target (e.g. /loop 10m /microfactory:plan-next); also takes an optional issue key to plan a specific issue.
GitHub Issues backend operations for the microfactory — find eligible issues, claim one with race verification, view, comment, and transition (statuses are mapped to labels), all via the gh CLI. Used by plan-next and implement-next when the configured backend is github. Not for general GitHub questions.
Run one implementation iteration of the microfactory — claim the next implementation-eligible issue from the configured backend, implement it (following the approved plan if one exists), run the tests, push (directly or via a feature branch + PR), and update the issue. Intended as a /loop target (e.g. /loop 20m /microfactory:implement-next); also takes an optional issue key to implement a specific issue.
Set up the microfactory for the current project. Interviews the user, writes .microfactory/config.yaml, authenticates the task backend (Jira via acli, GitHub via gh, or a local TODO.md), and starts the work loop. Use when the user wants to initialize, configure, or reconfigure the factory.
Jira backend operations for the microfactory — find eligible issues, claim one with race verification, view, comment, and transition, all via the acli CLI. Used by plan-next and implement-next when the configured backend is jira. Not for general Jira questions.