{"enrichment":{"faq":[{"a":"Refine transforms raw ideas into Definition-of-Ready PBIs by applying structured problem validation, requirements elicitation using BABOK techniques, and BDD-formatted acceptance criteria. The skill enforces hypothesis gates and mandatory stakeholder interviews to ensure teams have complete, testable scope before development begins.","q":"How does refine help convert ideas to product backlog items?"},{"a":"Refine guides you through writing GIVEN/WHEN/THEN acceptance criteria by first validating your problem hypothesis, then documenting each scenario in BDD format. This ensures acceptance criteria are testable, unambiguous, and directly tied to verified user needs rather than assumptions.","q":"How do you write GIVEN WHEN THEN acceptance criteria?"},{"a":"Refine supports dual estimation cycles covering story points, man-days, and complexity assessment. The skill also documents dependencies and production readiness factors, giving teams a complete picture of effort and risk before committing to a feature.","q":"What does refine include for estimating story points?"},{"a":"Refine enforces validation interviews with stakeholders to confirm scope, assumptions, and dependencies. By running these interviews early and documenting findings, teams catch misaligned expectations and hidden requirements before development, reducing rework and scope creep.","q":"How does refine validate problem hypotheses before building?"},{"a":"Refine applies a structured workflow combining BABOK elicitation techniques, domain research, hypothesis validation gates, and Definition-of-Ready checklists. The process moves from raw concept through stakeholder interviews, acceptance criteria authoring, and dual estimation to a production-ready PBI.","q":"What refinement workflow does refine recommend?"},{"a":"Refine's Definition-of-Ready checklist covers validated problem hypotheses, GIVEN/WHEN/THEN acceptance criteria, story-point and man-day estimates, documented dependencies, production readiness assessment, and stakeholder sign-off. This ensures every PBI is complete and testable before engineering begins.","q":"What is included in refine's Definition of Ready?"}],"shadow_tags":["requirements-elicitation","acceptance-criteria","hypothesis-validation","story-estimation","definition-of-ready","scope-management","stakeholder-interview","bdd-scenarios","backlog-grooming","delivery-readiness"],"summary_rewrite":"Refine transforms raw ideas into production-ready product backlog items through structured problem validation, requirements elicitation, and BDD-formatted acceptance criteria. The skill enforces hypothesis gates, mandatory user interviews, and dual estimation cycles to ensure teams have complete, testable scope before development begins."},"files":[{"bytes":71250,"path":".agents/skills/refine/SKILL.md","sha256":"7b7e11b998f4fee213025135d058575b23cd180fe48999e8a59ec64d7a38bfd9","url":"https://skillfed.io/files/duc01226/EasyPlatform/refine/335ca476/SKILL.md"}],"id":"duc01226/EasyPlatform/refine","links":{"html":"https://skillfed.io/duc01226/EasyPlatform/refine","md":"https://skillfed.io/duc01226/EasyPlatform/refine.md","repo":"https://github.com/duc01226/EasyPlatform"},"meta":{"agents_supported":["claude-code"],"first_seen":"2026-07-28","forks":1,"language":"C#","last_updated":"2026-06-18","license":"MIT","name":"refine","publisher":"duc01226","stars":7},"relations":{"categories":["product-management","business-analysis","agile-delivery"],"similar":[{"id":"duc01226/EasyPlatform/story"},{"id":"duc01226/EasyPlatform/dor-gate"},{"id":"duc01226/EasyPlatform/pbi-challenge"},{"id":"duc01226/EasyPlatform/plan"},{"id":"duc01226/EasyPlatform/business-analyst"},{"id":"duc01226/EasyPlatform/estimate-actual"},{"id":"duc01226/EasyPlatform/pbi-mockup"},{"id":"duc01226/EasyPlatform/workflow-idea-to-pbi"},{"id":"duc01226/EasyPlatform/workflow-spec-to-pbi"},{"id":"duc01226/EasyPlatform/debug-investigate"}]},"slug":{"owner":"duc01226","repo":"EasyPlatform","skill":"refine"},"version":"335ca476"}