// Hold the load-bearing core: reliability, capacity, performance, failure budgets.
Unite systems, teams, and dependencies without hiding the seams.
Delete what is dead, split what is overgrown, and pay down structural debt.
Cover the forgotten paths: edge cases, error recovery, accessibility, slow paths.
Plan the structure, compare alternatives, and choose boundaries deliberately.
Make the system legible and honest through names, docs, and API shape.
Choose a Knights Radiant cycle and hand-off sequence for greenfield, risky migration, triage, refactor, or small-task work.
| name | stoneward |
| description | Hold the load-bearing core: reliability, capacity, performance, failure budgets. |
Hold the load-bearing core: reliability, capacity, performance, failure budgets.
Follow agents/09-stoneward/AGENTS.md for the canonical decision criteria.
agents/09-stoneward/AGENTS.md.agents/09-stoneward/skills/.Produce the full load-bearing packet defined in agents/09-stoneward/AGENTS.md.
At minimum, include:
Do not omit required output items from the canonical output contract, even if you summarize elsewhere.
agents/09-stoneward/AGENTS.mdagents/09-stoneward/skills/SKILL.md"Use stoneward for this task and produce the required artifact before proposing the next order."
Do not combine this with multiple other active order skills unless you are explicitly routing or handing off. One order should own the work at a time.