mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-11 19:47:12 +03:00

Files

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

2.1 KiB

Raw Blame History

Product Lifecycle Bundle — Agent Instructions

Loading

Lifecycle routing

Load product-lifecycle umbrella SKILL.md for the phase routing table
Identify the current lifecycle phase from the table
Load references/phases.md for detailed phase contracts
Load the specialist skill(s) named in the phase row
Follow the specialist's method; do not re-derive it from the umbrella

Capability lookup

Load references/capability-map.md for capability → owning skill mapping
Load the owning skill directly

Nested skill loading

This bundle does not contain nested sub-skills. It composes specialist skills from the catalog. Each specialist skill is loaded on trigger when its phase is entered. The umbrella documents which skills load at which phase; it does not auto-load them.

Lifecycle evidence ledger

Every phase writes to a shared lifecycle evidence ledger. The ledger is the cross-phase handoff contract. Phase N+1 reads what phase N wrote and does not re-derive it. Ledger fields and conventions are defined in references/phases.md.

Stop and escalation

Every phase has explicit escalation behavior. A stopped/escalated lifecycle is a legitimate outcome — the ledger preserves what was learned. Stop conditions include: no viable problem (Phase 1), no strategic fit (Phase 2), experiment disproves hypothesis (Phase 5), readiness returns No-go (Phase 6), adoption fails (Phase 7), and justified retirement (Phase 9).

Reference files

File	Purpose
`references/phases.md`	Per-phase contracts with entry evidence, output artifacts, escalation behavior, completion criteria, and ledger spec
`references/discovery-brief.md`	Bundle boundary, comparison with existing bundles, surveyed skills, non-ownership statement
`references/capability-map.md`	Capability area → owning skill lookup table
`manifest.yaml`	Machine-readable bundle composition contract (schema v1): purpose, stages, included skills, handoffs, prerequisites, conflicts, eval suite

Environment

No environment variables required. No API keys, no services, no network dependencies.

2.1 KiB Raw Blame History