{"id":77042,"plugin_id":"plugins_6ab4123730588191bc9267b9458b2670","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:20.291Z","digest":"215750689c56ebd1efa82c8f5e5f237b62d18b26287547b1d3d84f91662983d1","against":null,"payload":{"description":"Define scoped changes to an existing app as a feature delta with testable acceptance criteria.","included_files":[],"name":"specify-feature","skill_md_contents":"---\nname: specify-feature\ndescription: Define scoped changes to an existing app as a feature delta with testable acceptance criteria.\n---\n\n# Specify Feature\n\n## When to use\nDefine scoped changes to an existing app as a feature delta with testable acceptance criteria.\n\n## Workflow\nCapture current and proposed behavior, specific user goal, entry point, affected roles, flow and all relevant states. Define data/API/auth impacts and edge cases; include non-goals, dependencies, rollout and reversal strategy. Preserve established design and architecture by default; reject unrelated rewrites.\n\nProduce a concise delta spec from `../../templates/feature-delta.md`. Give requirements stable IDs and map them to observable acceptance tests when engineering work will follow. Don't invent database tables or route names without inspecting code.\n\n## Deliverable and truthfulness\nLead with the decision or result, then show supporting evidence, explicit assumptions, risks, and a concrete next step. Adapt depth to the user's ask. If required tools or source material are missing, disclose the limit; do not simulate inspection, implementation or research. Never write/modify/deploy without relevant authorization.\n\nRelevant reference: `../../references/feature-specs.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}