Skills › BMAD Method › bmad-deep-recon › lifecycle.md

lifecycle.md

11 lines · skills/bmad-deep-recon/references/lifecycle.md at bd70c64

Runs code

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# Refresh and Deepen

3Lifecycle intents on an existing run folder.

Refresh and Deepen

Lifecycle intents on an existing run folder.

Raw lines 1 to 4

5## Refresh

7Read `<folder name>.md` and `.memlog.md` — never re-research from scratch. Build the refresh set mechanically: assemble the claims (`claim`, `class`, `pub_date`) from the ledger, map the pack's freshness bars to a months-per-class JSON, and run `uv run {skill-root}/scripts/recon_kit.py staleness <claims.json> --windows '<map>'` — the stale flags are the candidate set. Confirm it in one exchange, re-verify just those claims, and deliver a **delta report** (confirmed / changed / overturned, new sources) appended to `<folder name>.md` with the frontmatter `updated` bumped. Claims outside the set keep their status. An overturned load-bearing claim triggers an explicit warning naming the downstream artifacts that consumed it.

Refresh

Read <folder name>.md and .memlog.md — never re-research from scratch. Build the refresh set mechanically: assemble the claims (claim, class, pub_date) from the ledger, map the pack's freshness bars to a months-per-class JSON, and run uv run {skill-root}/scripts/recon_kit.py staleness <claims.json> --windows '<map>' — the stale flags are the candidate set. Confirm it in one exchange, re-verify just those claims, and deliver a delta report (confirmed / changed / overturned, new sources) appended to <folder name>.md with the frontmatter updated bumped. Claims outside the set keep their status. An overturned load-bearing claim triggers an explicit warning naming the downstream artifacts that consumed it.

Raw lines 5 to 8

Runs code scripts/recon_kit.py :7

9## Deepen

11Drill into one dimension or add a new one without touching the rest: mini plan gate, acquire → verify for that slice only (or a drafted follow-up prompt when the user's tool is better placed), merge into `<folder name>.md`, update only the synthesis sections the new material affects — a deepening that changes no conclusion says so.

Deepen

Drill into one dimension or add a new one without touching the rest: mini plan gate, acquire → verify for that slice only (or a drafted follow-up prompt when the user's tool is better placed), merge into <folder name>.md, update only the synthesis sections the new material affects — a deepening that changes no conclusion says so.

Raw lines 9 to 11