sweep_improvements
Runs Heimdall's improvement sweep on a project and answers with how many gaps became cards, how many cards came down and how many wait; calls no model and spends nothing.
Run Heimdall's improvement sweep on one project now and read what it did. The sweep reads the record for five structural gaps (a non-functional requirement without a measure, a story without a negative acceptance criterion, a business rule without a worked example, a data entity without an owner, an open risk without a mitigation) and leaves one improvement card per new gap on the review queue, titled with the record's reference; a card a person kept or dismissed is never proposed again, and a pending card whose gap was filled since is taken down. It calls no model and spends nothing. Read the cards with the project's suggestions over REST; deciding them stays with people.
The project is named by project_id. The same sweep runs weekly on every live project and when a brief import is fully decided, so running it is useful right after records were written. It needs import:create, a staff token and the project's assists on.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Arguments
project_id*stringUUID of the project to sweep.
What it returns
{ "data": { "proposed": 3, "retired": 1, "pending": 5 }}How it fails
RESOURCE_NOT_FOUNDunknown project_id, or a project outside the token's scope or the person's visibility.
FORBIDDENthe token is a client guest's, the holder's role on the project does not carry import:create, or the project's assists are off.
TOKEN_MISSING_ABILITYtoken lacks import:create.
How is this guide?
Last updated on