jaksa76

Assess the Agent Readiness level of the current project across all 11 criteria (C1.1–C8.2) and produce a structured report with the achieved level, per-criterion scores, gaps, and recommendations.

Verify readiness criterion C1.1 (Codebase Accessibility) in the current project. Reports fulfillment level 0–2.

Verify readiness criterion C2.1 (Setup Automation) in the current project. Reports fulfillment level 0–3.

Verify readiness criterion C3.1 (Architecture Depth) in the current project. Reports fulfillment level 0–3.

Verify readiness criterion C5.1 (Runnability) in the current project. Reports fulfillment level 0–2.

Verify readiness criterion C5.2 (Unit Test Coverage) in the current project. Reports fulfillment level 0–3.

Verify readiness criterion C8.1 (CI/CD Automation) in the current project. Reports fulfillment level 0–3.

Verify readiness criterion C8.2 (Observability) in the current project. Reports fulfillment level 0–3.

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.

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.

Implement a user story from docs/TODO.md end-to-end: planning, backend + frontend code, unit tests (Jest/supertest), Playwright e2e tests, and a refactor pass. Use this skill whenever the user asks to implement a story, work on a feature, or says something like "implement story NNNN" or "build the X feature".

Convert a USER-STORIES.md file into GitHub issues. Reads the file, groups stories into feature-area labels, merges near-duplicate stories, produces issues.json and create-issues.sh, then optionally runs the script. Use when the user has a user stories markdown file and wants to track them as GitHub issues.