Evaluate, secure, and ship
Finish and maintain the release-readiness skill
Complete the project through a real run, a handoff, and a maintenance loop driven by corrections rather than feature accumulation.
10 minute lesson
Now run the complete project against a real disposable repository or a safe copy of one.
Start with the user request: “Review this repository for release readiness. Produce the report, but do not commit, push, publish, or deploy.” Confirm the skill activates. Watch it discover project policy, identify commands, run checks, classify evidence, load only the relevant reference, fill the template, and validate the result.
Introduce one failure. Leave a required changelog entry missing or make one test fail. The report must change. If the final decision stays GO, fix the instructions or assertion before shipping.
Hand the skill to another person or agent host. Give no oral explanation. Ask them to install it, run the activation matrix, complete one review, and explain the authority boundary. Record every surprise. Portability includes the procedure, not only the directory format.
Maintain the skill from evidence. When a run misses a trigger, improve the description and rerun negative cases. When the agent makes a repeated workflow mistake, improve the procedure or add a gotcha. When it reinvents deterministic logic, consider a script. When content no longer changes outcomes, remove it.
Finish with a short release note: what the skill does, what it refuses to do, supported environments, evaluation scenarios passed, known limitations, and the next review date. You have not built a magic prompt. You have built a small operational system that can be inspected, tested, and improved.
Lesson completed