Summary
Rewrite the Known gaps bullet in
tools/spec-loop/specs/organization-adapters.md that says no validator check
enforces required files under organizations/<org>/. The check exists.
Background
The bullet reads "No structural validator check yet enforces required files in
organizations/<org>/ (currently README + organization.md by convention)." That
check shipped in #721 as validate_organization_structure, and it is a HARD
check, so the requirement is no longer convention-only.
Spec Known gaps sections are not just documentation: the spec-loop plan beat
reads them to choose the next work item, so a gap that describes already-shipped
code sends the loop at finished work.
Where to look
tools/spec-loop/specs/organization-adapters.md line 125 - the bullet to
rewrite.
tools/skill-and-tool-validator/src/skill_and_tool_validator/__init__.py -
validate_organization_structure is called at line 3706.
organizations/ - the live tree the check runs against. Note that
_template is deliberately excluded.
Verify by finding the call site, not the definition.
Acceptance criteria
Estimated effort
~30 minutes for someone new to the codebase.
Getting started
New to Magpie? Start with
Your first contribution.
Note: this issue was drafted by an AI-assisted mentoring tool and may contain
mistakes. A Magpie maintainer, a real person, will be the next to engage on it.
If something here looks wrong or unclear, please say so on the issue and a
maintainer will follow up. See
CONTRIBUTING.md
for how Magpie handles contributions.
Summary
Rewrite the
Known gapsbullet intools/spec-loop/specs/organization-adapters.mdthat says no validator checkenforces required files under
organizations/<org>/. The check exists.Background
The bullet reads "No structural validator check yet enforces required files in
organizations/<org>/(currently README + organization.md by convention)." Thatcheck shipped in #721 as
validate_organization_structure, and it is a HARDcheck, so the requirement is no longer convention-only.
Spec
Known gapssections are not just documentation: the spec-loop plan beatreads them to choose the next work item, so a gap that describes already-shipped
code sends the loop at finished work.
Where to look
tools/spec-loop/specs/organization-adapters.mdline 125 - the bullet torewrite.
tools/skill-and-tool-validator/src/skill_and_tool_validator/__init__.py-validate_organization_structureis called at line 3706.organizations/- the live tree the check runs against. Note that_templateis deliberately excluded.Verify by finding the call site, not the definition.
Acceptance criteria
and that
_templateis excluded.uv run --project tools/spec-validator spec-validate tools/spec-loop/specs/passes.
Estimated effort
~30 minutes for someone new to the codebase.
Getting started
New to Magpie? Start with
Your first contribution.
Note: this issue was drafted by an AI-assisted mentoring tool and may contain
mistakes. A Magpie maintainer, a real person, will be the next to engage on it.
If something here looks wrong or unclear, please say so on the issue and a
maintainer will follow up. See
CONTRIBUTING.md
for how Magpie handles contributions.