Workflow checks & maintenance · Improve
Improve Scoped
Implement the named behavior when no specialized recipe applies. Use the user’s requirement or a supported finding to establish the target and intended result; a prior audit document is optional.
MCP library 1.6.1 · Instruction library 1.6.1 · English technical instructions
← Back to searchUse this workflow
Connect Vibe Coding Library to a coding agent that supports MCP over Streamable HTTP. Choose Other / MCP agent for a neutral prompt, or a ready-made Codex or Claude Code invocation. Add your task details below.
Scope
Implement the named behavior when no specialized recipe applies. Use the user’s requirement or a supported finding to establish the target and intended result; a prior audit document is optional.
Procedure
- Locate the defining code, schema or configuration and directly affected contracts. Recover ordinary implementation context from current sources.
- Define acceptance and the compatibility/failure behavior that matters to the change. Ask only for an unresolved decision that changes it.
- Correct the owner and necessary producers/consumers, generated outputs or migrations. Preserve unrelated behavior and architecture.
- Run the native checks or controlled reproduction that exercise the selected contract. Record actual outcomes and required missing evidence.
Result
Report the implemented behavior, relevant changes, verification and remaining required work. Do not substitute another improvement when the target cannot be established.
Pass the expected/observed transition and actual changed paths to Behavior Check when verification needs a controlled reproduction beyond native tests. A failed check returns the same contract to this implementation step; correct the owner and repeat the affected scenario. Once acceptance is supported, run Patch Checking on the whole resulting patch until its clean marker or a concrete gate.
Workflow ID: scoped-polish · View the versioned source · Shared workflow and authority rules