mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-15 13:36:35 +03:00
Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
c0c7690724
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>
18 lines
993 B
Markdown
18 lines
993 B
Markdown
# AGENTS.md — Forward-Deployed Engineering Bundle
|
|
|
|
This is a thin orchestration bundle for embedded technical engagements. Its
|
|
umbrella `SKILL.md` owns continuity, artifacts, decision rights, adoption,
|
|
measurement, and generalization; routed catalog skills own specialist methods.
|
|
|
|
- Load the umbrella first, treat manifest stage skills as candidates, apply
|
|
`references/route-selection.md`, and load one primary specialist.
|
|
- Add a secondary specialist only for a named blocker, risk, or handoff.
|
|
- Keep the charter, workflow map, assumptions-decisions-risks ledger, and
|
|
evidence labels current across every handoff.
|
|
- Do not load nested helper skills; all routes point to top-level catalog skills
|
|
or existing canonical bundles.
|
|
- Stop and escalate when an action exceeds authority or the evidence required by
|
|
the current decision rule is missing.
|
|
- Keep artifacts private by default and complete the external-sharing gate before
|
|
anything leaves the authorized engagement context.
|