메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
| name | jira-tasks |
| description | 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. |
All operations use the acli CLI. Read acli-reference.md in this skill's directory for command details, and use acli <command> --help when unsure of exact flags. Configuration comes from .microfactory/config.yaml (project = Jira project key, jira_account_id = your assignee id).
Before the first operation, verify authentication with acli jira auth status; if unauthorized, stop and tell the user to run ! acli jira auth login.
Search with acli jira workitem search --jql "<JQL>" --json --paginate. Build the JQL by mode and the plan_by_default setting; always ORDER BY rank ASC and require assignee is EMPTY:
| Mode | plan_by_default | JQL conditions |
|---|---|---|
| planning | true | status = "To Do" AND (labels NOT IN ("skip-plan") OR labels is EMPTY) |
| planning | false | status = "To Do" AND labels IN ("needs-plan") |
| implementation | true | status = "Plan Approved" OR (status = "To Do" AND labels IN ("skip-plan")) |
| implementation | false | status = "To Do" AND (labels NOT IN ("needs-plan") OR labels is EMPTY) |
Example (implementation, plan_by_default false):
acli jira workitem search --jql "project = \"MYPROJ\" AND assignee is EMPTY AND status = \"To Do\" AND (labels NOT IN (\"needs-plan\") OR labels is EMPTY) ORDER BY rank ASC" --json --paginate
Other factory sessions may be claiming concurrently, so follow this optimistic-locking protocol exactly:
acli jira workitem assign --key <KEY> --assignee <jira_account_id> --yesPlanning (planning mode) or In Progress (implementation mode). If the transition is unavailable, warn and continue.acli jira workitem view <KEY> --jsonacli jira workitem view <KEY> --json (summary, description, labels, assignee).acli jira comment add --issue <KEY> --comment "<text>"acli jira workitem transition --key <KEY> --status "<status>" --yesStatuses used by the factory workflow: Planning, Awaiting Plan Review, Plan Approved (set by a human reviewer), In Progress, In Review, Done. Transitions may not exist in every workflow — treat failed transitions after work is done as warnings, not errors.