Make it your own.
Replace the bracketed inputs with a real, bounded task. Choose your sources and budget, review tool permissions, and decide what good looks like before starting. This is an example prompt, not an approved skill.
Download MarkdownEditable text · no signup
GOAL Investigate and propose [one small software change]. CONTEXT Repository or approved directory: [location] Current behavior: [what happens] Expected behavior: [what should happen] Acceptance criteria: [observable checks] Constraints: [budget, deadline, compatibility, files out of scope] TEAM Planner — identify affected areas and clarify the change. Builder — make the bounded change using approved tools. Reviewer — inspect behavior, changes and actual verification evidence. OWNER CHECKPOINT Ask when a product decision or new access is required. Save progress instead of assuming permission. DELIVERABLE 1. Summary of the proposed change 2. Changed files or artifacts 3. Commands and test results actually observed 4. Remaining issues and owner decisions DONE WHEN Acceptance criteria are checked and failures are reported honestly. Deployment is a separate decision. Do not change production by default. SKILL REVIEW Propose only a narrow procedure demonstrated by this work.
Review before reuse.
A successful result can suggest a reusable procedure. Review and approve its exact version separately. Do not include private source content in a shared skill unless that sharing is permitted.