MadaraUchiha-314/the-loop

MadaraUchiha-314/the-loop

Command

Part of the-loop

Start a work item with a brainstorm.md scratchpad BEFORE requirements — the optional root artifact. Iterate on it, then convert to requirements with /new-requirement.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Join an EXISTING, in-progress work item (issue or PR) as a contributor — walk the contribution loop toward a human-stated goal and success criteria, without the full spec chain.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Create design.md for a work item from its approved requirements.md (Phase 2 of the spec chain).

MadaraUchiha-314/the-loop

Command

Part of the-loop

Create tasks.md (a DAG of tasks) for a work item from its approved requirements.md, design.md and testing-plan.md.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Create testing-plan.md for a work item from its approved requirements.md and design.md — how the item will be proved, before the task DAG.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Create a work-item ticket (GitHub issue / Jira) from an existing requirements.md, then promote its draft spec folder to docs/specs/ /.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Do an ad-hoc, tactical task on a work item with NO PDLC process — no spec chain, no phase gates, no review chain. Work, ask follow-ups on the thread, continue until the requester says it is done.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Execute the task DAG for a work item — implement, verify against the testing plan, self-check, self/critic-review (implementation → verification → review).

MadaraUchiha-314/the-loop

Command

Part of the-loop

Finalize a work item after all tasks are done — cleanup (currently closing the ticket) and mark the work complete.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Initialize "the-loop" in the current repository — scaffold .the-loop/, the docs trees (specs, capabilities, decisions, learnings) and a validated config, establishing the config with the user via a guided, schema-driven onboarding. Idempotent, non-clobbering, with drift detection.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Start a new work item by drafting a requirements.md BEFORE a ticket exists — in a temporary spec folder. Follow with /create-ticket.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Review a pull request against an authorized reviewer's brief — answer their questions, examine their angles, run their validations, and converse until they say done. Change NO code.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Reconcile a project's "the-loop" files with the installed plugin version — create missing files and migrate schemas. Idempotent, non-clobbering, with --dry-run.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Execute a work item's testing-plan.md after implementation — run the planned activities, record results, commit the evidence (verification phase).

MadaraUchiha-314/the-loop

Command

Part of the-loop

Run "the-loop" on a work item (GitHub issue or Jira id) end-to-end — requirements → design → testing plan → tasks → execute → verify, with self/critic review.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Report the current status of a work item by reading its spec files (requirements/design/tasks) and execution log. Read-only.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Ask a human a question on the work item — the way a spawned agent escalates.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Operate the communication channels — the back-and-forth surfaces beside the work item, starting with the Slack bot (issue-245).

MadaraUchiha-314/the-loop

Command

Part of the-loop

Evaluate a work item's process-graph nodes against its checked-in artifacts, and report what is unmet.

MadaraUchiha-314/the-loop

Command

Part of the-loop

The seam by which the harness doing the work hands it to a different harness for a critic round, and reads back what it said.

MadaraUchiha-314/the-loop

Command

Part of the-loop

One self-diagnosis scan, on demand: read the-loop's own event log for harness-level failures — error-level events, terminal give-ups — debug each new one in an isolated agent one-shot, and file the findings as an issue on the-loop's own repository, labeled the-loop: self-diagnosed (issue-242).

MadaraUchiha-314/the-loop

Command

Part of the-loop

Query the structured event log — the end-to-end record of what the-loop's CLI processes decided, and why.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Inspect and drive the-loop's process graph — the PDLC as an executable graph of nodes with entry and exit hooks, rather than a set of labels somebody remembers to move.

MadaraUchiha-314/the-loop

Command

Part of the-loop

Command "index" from MadaraUchiha-314/the-loop, covering commands, the control plane, daemon commands, repo-scoped commands and maintenance.