{"id":77012,"plugin_id":"plugins_6ab41ed5b8c4819199eb5bbf91ce25f5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:18.801Z","digest":"ed553a0fb414197762474a28f577ea6a6a2b948280c5254c31590af0af645e56","against":null,"payload":{"description":"Implement a focused feature or change in an existing repository while preserving established structure, API contracts and user behavior.","included_files":[],"name":"implement-feature","skill_md_contents":"---\nname: implement-feature\ndescription: Implement a focused feature or change in an existing repository while preserving established structure, API contracts and user behavior.\n---\n\n# Implement Feature\n\nUse this skill only for its stated purpose. Follow the shared source-of-truth, permission and evidence rules in `../../references/workflow-contract.md`. Read `../../references/feature-implementation.md` for detailed method when necessary.\n\n## Procedure\n1. Define desired behavior, non-goals, changed interfaces and acceptance criteria.\n2. Inspect sibling patterns and affected tests before touching files.\n3. Implement one coherent vertical slice; include meaningful validation, failure behavior and access checks.\n4. Add regression and boundary tests proportionate to risks; run repository commands where available.\n5. Summarize exact changes, compatibility impact and any rollout requirements.\nAvoid broad rewrites, invented dependencies, and unsolicited deployment.\n\n## Handoff rule\nState actual artifacts or grounded code findings and validation status. Never invent file paths, executed tests, tool access, or completed subagent work. Keep output proportionate to the user request.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}