domains / families / software-engineering / repo-foundation

repo-foundation

authentic

Implement features, fixes, modules, contract migrations, and resumed work while preserving user edits and authorized public contracts.

When to use

• Use when the user asks to add a feature, fix a bug, or start a module in an existing project.
• Use when establishing the minimum foundation for a new repository or subsystem.
• Use when requirements authorize a schema, public-contract, ownership, or architecture migration.
• Use when resuming unfinished work or reconciling stale notes with repository evidence.

When not to use

• Repository instructions and actual callers are required to establish local contracts; the skill cannot infer missing product requirements reliably.
• Atomic replacement examples depend on the target filesystem and do not establish crash durability on every platform.
• Relevant passing checks establish only their exercised scope; they do not prove that all requirements or failure modes are covered.
• Companion review is optional when unavailable; same-agent self-review is not independent review.
• **Trivial edits:** Skip this skill for typos, isolated script adjustments, or formatting-only changes: the overhead is not worth it.

Skill page

Source