Writing a stack pack — the flow

Writing a stack pack — the flow A workflow diagram generated by Archify. 01 / 1. Detection · once/run 02 / Fallback: generic 03 / 2. Path resolution · once/run 04 / 3. Consumption: leaves 05 / 3. Consumption: env-checker 06 / 3. Consumption: advisor/modeler Target repo · 1. Detection · once/run Target repo scripts/mem-scan.sh · 1. Detection · once/run scripts/mem-scan.sh .swarm/context-pack.md · stack: your-pack-name · 1. Detection · once/run .swarm/context-pack.md stack: your-pack-name stack: generic · Fallback: generic stack: generic ls -d skills/pack-<name> · → <absolute path> · 2. Path resolution · once/run ls -d skills/pack-<name> → <absolute path> 8 pack-aware leaves · Read commands/conventions/boundaries/precedents → own judgment · 3. Consumption: leaves 8 pack-aware leaves Read commands/conventions/boundaries/precedents → own judgment env-checker · via requirements-orchestrator · 3. Consumption: env-checker env-checker via requirements-orchestrator pattern-advisor / domain-modeler · honor stack:, read nothing · 3. Consumption: advisor/modeler pattern-advisor / domain-modeler honor stack:, read nothing pack: <path> header --pack <path>/requirements.json stack: line only marker(s) found no marker matches Legend Agent logic Context / trace External system