Tasks: the-loop (create itself)

Phase 3. The implementation DAG for the-loop. v0 tasks (1–15) are done and form the current PR; deferred tasks (16–25) are the planned forward DAG and remain unchecked until taken up as follow-up work items (per decision-003). Each task references the requirement(s) it satisfies and its dependencies.

v0 — foundation (this PR)

• [x] 1. Plugin distribution: plugin.json, marketplace.json
  • Depends on: none — Requirements: R7
• [x] 2. Project footprint: config.schema.json (+ workflow, webhooks), default config.yaml, manifest.yaml, external-tools.md, collaborators.yaml
  • Depends on: none — Requirements: R2, R3, R5, R7
• [x] 3. Templates: epic/story/bug + requirements/bugfix/design/tasks/execution-log/ decision/learning
  • Depends on: 2 — Requirements: R1, R4, R6
• [x] 4. Commands: init, work-on (3-phase), upgrade-the-loop
  • Depends on: 2, 3 — Requirements: R4, R7
• [x] 5. Skill + reference docs (workflow, tooling, collaboration, observability, automation) + SessionStart hook
  • Depends on: 2 — Requirements: R2, R3, R4, R5
• [x] 6. Knowledge: architecture index, decisions 001–006, learnings index
  • Depends on: none — Requirements: R6
• [x] 7. Self-referential 3-phase spec + execution log for issue #1
  • Depends on: 3 — Requirements: R4, R6
• [x] 8. README with install/usage/roadmap
  • Depends on: 1, 4 — Requirements: R7
• [x] 9. Phase state machine + labels modeled in config/commands
  • Depends on: 2, 4 — Requirements: R4
• [x] 10. Validate (JSON, schema, manifest tree); commit; push
  • Depends on: 1–9 — Requirements: R2, R7
• [x] 11. CLI: extensible the-loop Python CLI (zero-dep core) + gh-webhook start|stop receiver (HMAC verify, /health, pytest); webhooks.ghWebhook config
  • Depends on: 2 — Requirements: R9, R8 (receiver)
• [x] 12. the-loop's own quality gates: ruff (lint+format), pyright, pytest, markdownlint, schema validation, Conventional Commits via commitizen (commit-msg) — via pre-commit + GitHub Actions CI (same tooling local & CI) + root Makefile + .claude/settings.json
  • Depends on: 11 — Requirements: R2
• [x] 13. User-interaction principles: config.userInteraction (mermaid diagrams, condensed/prioritized PR summaries, mandatory user education) encoded in schema + both configs, and operationalized in SKILL/work-on/reference/collaboration.md
  • Depends on: 2, 5 — Requirements: R10
• [x] 14. Granular per-phase commands: new-requirement, create-ticket, create-design, create-tasks-plan, execute-tasks, finish-tasks, work-status (with work-on as superset); pre-ticket draft-folder flow. SKILL/README/workflow updated
  • Depends on: 4 — Requirements: R7
• [x] 15. Review-driven robustness (issues #3–#10): review method (reviewing.md), learnings lifecycle (selfImprovement), risk-tiered autonomy (autonomy), TDD (tdd), minimalism (minimalism.md/minimalism), conflict log (conflicts.md), open critic harness enum, idempotent init/upgrade (--dry-run, drift report)
  • Depends on: 4, 5, 9 — Requirements: R11 (each item has its own ticket #3–#10)

Deferred — runtime & integrations (follow-up work items)

• [ ] 16. Make init actually scaffold (write files, detect tooling, create labels)
  • Depends on: 4 — Requirements: R7
• [ ] 17. Scaffold per-language tooling into user projects: uv/bun, pytest/vitest, playwright, ruff/oxlint, pyright/tsc, markdownlint, with root scripts
  • Depends on: 2 — Requirements: R2
• [ ] 18. Scaffold pre-commit/pre-push hooks + CI into user projects (same-tooling rule)
  • Depends on: 17 — Requirements: R2
• [ ] 19. Multi-entity testing: local linking, podman service orchestration, local-vs- remote selection
  • Depends on: 17 — Requirements: R2
• [ ] 20. Observability wiring: shared logger, configurable levels, chrome-devtools MCP browser logs
  • Depends on: none — Requirements: R3
• [ ] 21. Messaging integrations (slack/whatsapp/email) for escalations
  • Depends on: none — Requirements: R5
• [ ] 22. Predictability: decide hooks vs custom code/scripts; enforce PDLC steps (incl. hard-enforcing mandatory user education, R10.4)
  • Depends on: 5 — Requirements: R4, R10
• [ ] 23. Route received webhook events (PR comments, Actions) from the CLI → harness
  • Depends on: 11, 22 — Requirements: R8
• [ ] 24. Remote-workspace auto-trigger on ticket creation ("the dream")
  • Depends on: 23 — Requirements: R8
• [ ] 25. Project-wide DAG orchestration (depends-on/blocked-by) + Cursor packaging
  • Depends on: 22 — Requirements: R8, R7

Dependency graph (DAG)

v0: {1,2,6} → 3 → {4,5,7,9} → 8 → 10; 2 → 11 → 12; {2,5} → 13; 4 → 14; {4,5,9} → 15 (2 also feeds 4/5/9; 1 also feeds 8). Deferred: 4 → 16; 2 → 17 → {18,19}; 20,21 independent; 5 → 22; {11,22} → 23 → 24; 22 → 25.

Checkpoints

• v0: after task 10 — JSON + schema validation + manifest tree check; after task 11 — pytest for the CLI; after task 12 — pre-commit run --all-files green (see execution-log).
• Each deferred task: tests at logical checkpoints per reference/workflow.md.