skills-maker

To create skill fixtures using runtime evidence, you must first read the convergence materials and prioritize the handoff bundle. This ensures correct behavior aligns with real runtime evidence rather than generic patterns, reducing trial-and-error.

Auditing skills against runtime handoff artifacts involves reading the established handoff information first, then evaluating skill behavior. This process validates correct behavior and explicitly flags any missing evidence gaps rather than silently proceeding.

You can refactor skills using runtime evidence, but the process requires explicitly labeling missing evidence gaps. It prioritizes reading the handoff bundle first and will flag missing evidence to prevent silent progression with incomplete data.

Evidence-based skill creation relies on real runtime handoff artifacts to determine correct behavior, whereas generic patterns depend on assumptions. This approach forces explicit gap labeling when evidence is missing, preventing missing requirements.

Yes, you need to read convergence materials before auditing skill fixtures. The workflow requires reading the established handoff information first to ensure audit decisions and outcomes are based on actual runtime evidence.

Skill fixture creation requires a handoff bundle because tasks often depend on real runtime evidence. The bundle provides the necessary artifacts to produce explicit create, refactor, or audit outcomes while preventing missing requirements.