grimoire-implement
Implement the authorized behavior from the original source and available plan context; a persisted plan is not required.
Standalone, do not start grimoire-loop; it requires explicit user invocation.
Under orchestration, the caller's execution contract takes precedence over this skill's standalone defaults.
Source and scope
Resolve intended outcomes, constraints, and acceptance criteria from the supplied conversation, ticket, spec, or plan. User intent outranks incidental plan details. Ask when ambiguity would materially change scope, safety, or an irreversible decision; otherwise state bounded assumptions.
Inspect relevant implementation and consumers. Plans predict files and types, not immutable boundaries. When repository evidence invalidates the approach, make authorized adaptations and return material deviations to the coordinator; ask before changing approved scope or irreversible decisions.
Change boundaries
Implement coherent units, allowing coupled files to change atomically. Include adjacent cleanup only when necessary for correctness, removing duplication introduced by the change, or materially reducing its risk. Avoid unrelated formatting and opportunistic rewrites.
An abstraction may be justified by current boundary value—test substitution, dependency inversion, external isolation, invariant enforcement—even with one implementation. Do not add interfaces solely for predicted future variation. For consequential ownership or boundary tradeoffs, consult principles.md; these are heuristics, not syntax rules.