Decomposes approved product stories into dev tasks, roadmaps, experiments, and POC gates.
npx skills add https://github.com/Dozyboy/VSF --skill hs-shape-dozyboy
Please help me install this Agent Skill. Skill: hs:shape Source: https://github.com/Dozyboy/VSF/tree/main/Day2_VSF/Demo1/harness/plugins/hs/disabled-skills/shape Command: npx skills add https://github.com/Dozyboy/VSF --skill hs-shape-dozyboy
serves field. - Roadmap & Effort Rollup: Aggregate milestones and effort figures from the task sidecar, mapping story sizes (S/M/L) to day ranges and summing explicit task estimates. - Market Experiment Specs: Pre-register a hypothesis, design, and decision rule before an experiment runs, then apply a PO-supplied result against that rule to compute a deterministic hit/partial/miss verdict. - Technical POC Gate: Read code-review and verification verdict artifacts and close a POC only when both read PASS, then hand a plan-intake brief to the planning stage. - Use Case: After a story is approved, invoke the task flag to generate TASK records, roll them into a roadmap with effort estimates, and gate the roadmap on a closed POC before counting the work as feasible. ## Quick Start Ask the AI to decompose the approved story into dev tasks and roll them up into a roadmap with effort estimates using this skill.High-intent search queries and answers about installing and using this skill.
Invoke the skill with the --task flag and a story id to author a task sidecar record whose serves field points at that story. Passing an epic or prd id fans out to descendant stories after a read-only scope preflight, authoring one task per chosen story.
The rollup maps a story's size field (S/M/L) to a day range through a configurable YAML table, while an explicit estimate on a task record always wins. Estimates are parsed and summed into a min-max day range, with unparsable entries skipped rather than failing the build.
No. It only pre-registers the experiment spec (hypothesis, design, decision rule) before anything runs and later applies a PO-supplied metric result against that rule. Soliciting customers, running splits, or fetching metrics is explicitly out of scope and guarded by source-level checks.
A POC closes only when both the code-review verdict and the verification verdict read back as exactly PASS. PASS_WITH_RISK, BLOCKED, or missing artifacts leave the POC open, and a closed POC is a precondition before a roadmap rollup counts the work as feasible.
No. All writes are contained under docs/product/shape/ through a path-containment helper that raises on any escape attempt toward the PO-owned tree. The story graph is only read, never mutated, and this is enforced in code rather than by convention.
MaxGiu67Generate user stories with DATO-QUANDO-ALLORA acceptance criteria from PRD documents.
fanciveConvert tech plans into test-first implementation pipelines with Codex-based code review.
galatanovidiuRun tests, triage code review, and validate acceptance criteria into checks.md.
rpmcdougallGenerates user stories, sprint plans, backlog priorities, and retro action items for agile teams.