Files
magnus919_agent-skills/forward-deployed-engineering/references/lifecycle-and-artifacts.md
T
Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> c0c7690724 feat(flatten): move bundle dirs to repo root
Move the 8 directories under bundles/ to the repo root via git mv and
remove the now-empty bundles/ directory. Replace the "bundles" entry in
pyproject.toml [tool.deptry] extend_exclude with the 8 moved dir names so
the moved trees stay excluded from Python dependency analysis.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
2026-08-14 15:26:27 -04:00

24 lines
1.1 KiB
Markdown

# Lifecycle and Artifacts
The lifecycle is a continuity contract, not a claim about industry standard
practice. The nine-stage contract — required question, minimum output, and
stop condition per stage — lives in [SKILL.md](../SKILL.md#lifecycle) and is
the single source of truth for stage expectations.
Every stage records entry evidence, the artifact produced, the accountable
decision maker, unresolved unknowns, and the next handoff in the shared
records below.
## Shared record fields
For every stage record: date, stage, accountable lead, decision authority,
entry evidence, work performed, source/evidence label, observed result,
unknowns, risks, decision rule, decision, commitment, owner, due date, and next
handoff. A stopped engagement remains a valid output if the stop reason and
learning are preserved.
Use the canonical [stage-handoff record](../templates/stage-handoff-record.md)
for those fields. Maintain [engagement status](../templates/engagement-status.md)
as the concise current-state view; it supplements rather than replaces the
stage evidence and handoff record.