M3 — Stage 1: Implement #4

New issue

david · 2026-07-24T00:53:30Z

david commented

2026-07-24 00:53:30 +00:00

Goal: produce an implementation diff from the Jira context.

Tasks

Wrapper prompt: implement the ticket, follow repo conventions; input = jira-context.json; exit = working-tree changes satisfying acceptance criteria.
Compose system prompt from IMPLEMENT_SKILL_PATH (+ default fallback).
Tools: read, bash, edit, write, grep, find, ls.
Preflight: verify clean/known git state; capture base ref.
After the turn, capture git diff -- . ':(exclude).pi-loop' → implementation.diff.

Depends on: M1, M2.

Validation: on a sample repo+ticket, code changes appear and implementation.diff is captured (excludes .pi-loop/). If IMPLEMENT_SKILL_PATH unset, stage runs degraded and is recorded.

**Goal:** produce an implementation diff from the Jira context. ### Tasks - [ ] Wrapper prompt: implement the ticket, follow repo conventions; input = `jira-context.json`; exit = working-tree changes satisfying acceptance criteria. - [ ] Compose system prompt from `IMPLEMENT_SKILL_PATH` (+ default fallback). - [ ] Tools: `read, bash, edit, write, grep, find, ls`. - [ ] Preflight: verify clean/known git state; capture base ref. - [ ] After the turn, capture `git diff -- . ':(exclude).pi-loop'` → `implementation.diff`. **Depends on:** M1, M2. **Validation:** on a sample repo+ticket, code changes appear and `implementation.diff` is captured (excludes `.pi-loop/`). If `IMPLEMENT_SKILL_PATH` unset, stage runs degraded and is recorded.

david referenced this issue from a pull request that will close it,

2026-07-24 10:55:32 +00:00

M3 — Stage 1: Implement #13

david closed this issue

2026-07-24 20:32:29 +00:00

david referenced this issue from a commit

2026-07-24 20:32:30 +00:00

M3 — Stage 1: Implement (#13)

david referenced this issue

2026-08-17 02:51:14 +00:00

229: Friction: aggregate recompute at end of run (.pi-loop/friction/) + console Friction: line #244

Sign in to join this conversation.