Skip to content

A full-mode feature keeps one plan file and one closing record, and prints only the checklist groups it needs - #196

Merged
ziadantar90 merged 1 commit into
mainfrom
lean-full-records
Nov 4, 2026
Merged

ziadantar90 merged 1 commit into
mainfrom
lean-full-records

Conversation

@ziadantar90

Copy link
Copy Markdown
Collaborator

What this adds

  • One plan file. harness/templates/feature.md is removed. The owner's request now goes in plan.md § Request.

  • One closing record. harness/templates/retro.md is removed. The feature's learnings file holds the retro:

    • § What went wrong, one line per miss with its cause and evidence, or None.;
    • action items, only from those lines.

    harness/SETUP.md § Retrospective is shorter, and the rules on items stay. When the prune folds an entry, it keeps the miss lines, so a later prune can see a problem come back. scripts/evidence.sh now finds bug mode by the Escaped line.

  • Fewer hand-off checks.

    • After a QA pass, the main chat reads QA's record instead of re-running the checks.
    • Screenshots are checked once, before QA.
    • The project fact docs become Full-stack plan steps, each with an acceptance criterion QA checks.
    • The close takes three steps: the cost script, the learnings file, then the commit and the prune counter in one call.
  • Only the checklist groups a plan needs, in one call. The group index moves into harness/TECHNICAL_LEAD.md, which the main chat reads in full anyway. No skip condition is narrower than before:

    • Planning, Testing and Process always run;
    • the Security, Data and Release conditions now also cover changes to existing permissions, schemas and schedules.
  • Self-test: a new check_lean_records check covers:

    • the removed templates and any doc that still names them;
    • § Request and § What went wrong;
    • no re-run after QA, and the close;
    • the index against the checklist's groups, ranges and skip conditions;
    • the step 4 that other docs cite.

    The evidence.sh test gains a bug-mode case.

  • The update note updates/2026-11-04-lean-full-records.md has a reviewed: line, because Full-stack's ownership limits change. There is also a changelog fragment.

Checks:

  • STRICT=1 bash scripts/kit-selftest.sh passes: 4 fixtures, 0 problems.
  • check-updates and check-lessons report 0 problems.
  • On the negative test, the old kit fails the new checks (34 problems on nextjs-supabase).

Generated by Claude Code

@ziadantar90 ziadantar90 self-assigned this Nov 4, 2026
@ziadantar90
ziadantar90 merged commit 1813513 into main Nov 4, 2026
2 checks passed
@ziadantar90
ziadantar90 deleted the lean-full-records branch November 4, 2026 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant