synthesize-tech-skill-from-playbook

You generate ephemeral skills at runtime by providing a canonical stack playbook and a detected stack record to the synthesizer, which applies deterministic template substitution to produce a SKILL.md file without LLM reasoning.

Deterministic skill synthesis is a runtime process that converts playbook sections into an ephemeral SKILL.md using pure template substitution, eliminating manual error-prone work and ensuring consistent extraction instructions for detected stacks.

Synthesized SKILL.md files and a synthesis-record.yaml are written into short-term memory under a temp-skills path and marked ephemeral, ensuring they can be cleaned up automatically during a final Tether operation.

Yes, the synthesis process optionally symlinks or copies the generated SKILL.md into the .claude/skills directory, enabling downstream components to discover and dispatch the correct stack-specific logic during decode operations.

When parse or I/O errors occur during skill synthesis, the process fails safely and returns structured what_failed codes, validating input paths before writing any artifacts to prevent corrupted extraction logic.

Yes, a detected stack record and a canonical playbook path are required inputs to synthesize tech-specific skills, ensuring the generated extraction logic is correctly scoped to the identified technology stack.