Transform approved PRDs into sprint-based technical specifications and runtime bundles.
npx skills add https://github.com/iurykrieger/claude-yoke --skill tech-spec-iurykrieger
Please help me install this Agent Skill. Skill: tech-spec Source: https://github.com/iurykrieger/claude-yoke/tree/main/skills/tech-spec Command: npx skills add https://github.com/iurykrieger/claude-yoke --skill tech-spec-iurykrieger
Phase 2 — Technical specification planning becomes automated: turning approved PRDs into structured sprint specs, DoDs, and per-sprint runtime bundles. The skill orchestrates a three-stage blueprint (LLM drafts the sprint index, bash scaffolds empty per-sprint files, LLM fills each sprint) and stores artifacts under .yoke/specs/ and .yoke/sprints/. It pauses at Trigger 2 until approval, ensuring a controlled, auditable transition to Phase 3.
Initiate the workflow by providing an approved PRD to /yoke:tech-spec to generate the sprint index, scaffold per-sprint files, and iteratively fill them.
High-intent search queries and answers about installing and using this skill.
To convert an approved PRD into sprint-ready technical specifications, the skill drafts a sprint index using an LLM, scaffolds empty sprint files via Bash, and fills each file with objectives, tasks, and DoDs before requiring approval.
Generating per-sprint runtime bundles works through a three-stage workflow: LLM drafts the sprint index, Bash deterministically scaffolds empty per-sprint files, and the LLM fills each file with strict binary acceptance criteria.
Yes, you can enforce an approval workflow because the skill pauses at Trigger 2, requiring explicit approval before all sprints transition to Phase 3, ensuring a controlled and auditable development handoff.
The best way to structure sprint tasks with strict binary acceptance criteria is by having the LLM populate each sprint file with functional criteria, sensors, and tasks gated by a Trigger 2 approval.
Technical specification and sprint artifacts are stored as markdown files under .yoke/specs/<slug>.md and .yoke/sprints/<slug>-sNN>.md, keeping all sprint planning outputs organized in your workspace.
MazenMradProduce a formal Sprint Change Proposal for approving significant sprint changes.
SvenMarcusIdentify and resolve bugs through OpenAgent's four-phase approval-gated debugging workflow.
shaman007Parse task identifiers from spec-kit documentation and create GitHub issues.
kid-sidWrite testable requirements and acceptance criteria for PRDs and user stories.
