Guide refinement of BMILD workflow artifacts using curated elicitation methods.
npx skills add https://github.com/micfre/BMILD --skill bmild-elicit
Please help me install this Agent Skill. Skill: bmild-elicit Source: https://github.com/micfre/BMILD/tree/main/.agents/skills/bmild-elicit Command: npx skills add https://github.com/micfre/BMILD --skill bmild-elicit
BMILD workflow artifacts (requirements, UX designs, architecture decisions, slice definitions) often contain unstated assumptions, vague requirements, and missing perspectives that lead to rework, flawed implementations, and missed project goals. This skill solves that problem by guiding users through rigorous, targeted elicitation to strengthen their work before implementation.
Invoke the bmild-elicit skill with your draft BMILD artifact to start a guided session that surfaces hidden assumptions, stress-tests decisions, and refines your content for rigor.
High-intent search queries and answers about installing and using this skill.
To refine BMILD specs and surface hidden assumptions, you can use a guided elicitation process that applies targeted methods to identify vague requirements and missing perspectives before implementation begins. This enforces strict adherence to a curated registry of over 50 proven elicitation methods.
Validating unclear acceptance criteria in a draft slice definition involves guiding users through targeted elicitation methods to surface missing edge cases and validate underlying assumptions. This context-aware refinement automatically identifies your content type to recommend the best-fit approach.
Assumption testing for architecture decision records works by applying targeted elicitation methods to stress-test decisions and identify unstated assumptions. The workflow iterates until you explicitly proceed with the refined content, ensuring all gaps are addressed.
Yes, you can use targeted elicitation methods to fix vague requirements documents by selecting from a standardized registry of over 50 proven techniques. This eliminates guesswork in method selection by matching approaches to your content's specific weaknesses.
Spec-driven development refinement respects BMILD persona ownership boundaries by only refining content you explicitly authorize. It suggests the appropriate persona for cross-domain gaps instead of overstepping into owned work, maintaining strict boundary controls.
johangm90Design software architecture with bounded contexts, vertical slices, ADRs, and PRDs.
xhyqaqConvert approved product specifications into structured acceptance criteria with pass/fail checks.
nishantnaagnihotriEnforce cross-agent domain ownership and route cross-domain work through the orchestrator.
dige04Apply structured problem-solving techniques to analyze and document complex problems.
