terryyin
@terryyin
Public Skills
dough-slice-planning
by terryyin
Plans one understood, bounded story as an executable sequence of Behavior/Structure slices with outside-in proof and safe stopping points. Use when a selected story is ready for implementation planning. Stays within the triggering instruction's execution authority: finish after writing and reporting the plan unless that instruction explicitly also requests execution. Reports remaining slice-specific concerns or a limited no-concerns finding; does not prescribe the next workflow action or certify execution readiness. Concern evidence does not authorize execution.
dough-slice-plan-refinement
by terryyin
Refines an existing executable plan in place into smaller, proof-owned Behavior/Structure slices. Use after dough-slice-planning when slices are complex, sizing confidence is low, or execution overruns. Creates no new plan and does not change the selected story outcome.
dough-slice-planning
by terryyin
Plans one understood, bounded story as an executable sequence of Behavior/Structure slices with outside-in proof and safe stopping points. Use when a selected story is ready for implementation planning. Recommends dough-slice-plan-refinement only for complex, low-confidence, or over-budget slices; does not implement the plan.
dough-execution-retrospective
by terryyin
Reviews one completed or in-progress plan execution against its original story, aggregate commit set, and current project truth. Use for an execution retrospective, product review, or backlog recommendation even when cleanup removed the plan or the user supplies only a partial reference. --skip-process and --skip-product omit those reviews independently. May plan unresolved implementation findings and recommend product work; never implements them.
dough-slice-plan-refinement
by terryyin
Refines an existing executable plan in place into smaller, proof-owned Behavior/Structure slices. Use after dough-slice-planning when slices are complex, sizing confidence is low, or execution overruns. Creates no new plan and does not change the selected story outcome.
dough-adr-awareness
by terryyin
Use and cite this project's current Accepted Architectural Decision Records for architecture-shaped work, follow supersession, surface conflicts instead of silently drifting, and preserve human ownership of decisions and exceptions. Use when a task mentions ADRs or architectural constraints, may reverse an existing decision, or crosses architecture areas defined by this project.
dough-execute-plan
by terryyin
Executes the slices in an executable plan for one selected story, with independent refactoring, selective formatting, plan updates, commit and push, and asynchronous CI repair. Use to execute a plan, run a plan, or execute slices; does not execute a seed or decide story scope.
dough-post-change-refactor
by terryyin
Refactors concepts implicated by the current uncommitted change before commit. Includes untouched code needed for coherence, stops before unapproved cross-subsystem refactoring, and tests only after edits. Use after a slice, for post-change refactoring, or to clean up the current change.
dough-product-backlog
by terryyin
Maintains and reprioritizes a product backlog list of story references. Use to add, reorder, or complete backlog items. Excludes classroom and workshop exercise backlogs.
dough-resplit-story
by terryyin
Resplits a large story after slice-plan refinement into smaller stories and mapped slice plans. Use when resplitting is requested, including after a more-than-15-slices recommendation. Leaves the first story and plan refined; later plans await story refinement and backlog priorities are reconsidered.
dough-story-decomposition
by terryyin
Challenges and decomposes a broad product problem into ordered Valuable/Visible/Vertical stories with rough effort hypotheses. Use when the parent problem, candidate stories, or learning priority are unresolved. Writes one non-executable seed.
dough-story-refinement
by terryyin
Clarifies selected stories before execution planning by establishing goal, scope, and key examples in each story's seed. Adds UI or architectural detail only when needed. Use for selected-story refinement, not broad problem decomposition, candidate selection, or slice sizing.
dough-update
by terryyin
Apply the latest released Open Dough guidance from this project's recorded source, or from a supplied repository URL on first install. Use when the user asks to update Open Dough or invokes dough-update.
dough-update
by terryyin
Apply the latest released Open Dough guidance from this project's recorded source, or from a supplied repository URL on first install. Use when the user asks to update Open Dough or invokes dough-update.
dough-adr-awareness
by terryyin
Use and cite this project's current Accepted Architectural Decision Records for architecture-shaped work, follow supersession, surface conflicts instead of silently drifting, and preserve human ownership of decisions and exceptions. Use when a task mentions ADRs or architectural constraints, may reverse an existing decision, or crosses architecture areas defined by this project.
dough-execute-plan
by terryyin
Executes the slices in an executable plan for one selected story, with independent refactoring, selective formatting, plan updates, commit and push, and asynchronous CI repair. Use to execute a plan, run a plan, or execute slices; does not execute a seed or decide story scope.
dough-post-change-refactor
by terryyin
Refactors concepts implicated by the current uncommitted change before commit. Includes untouched code needed for coherence, stops before unapproved cross-subsystem refactoring, and tests only after edits. Use after a slice, for post-change refactoring, or to clean up the current change.
dough-product-backlog
by terryyin
Maintains and reprioritizes a product backlog list of story references. Use to add, reorder, or complete backlog items. Excludes classroom and workshop exercise backlogs.
dough-resplit-story
by terryyin
Resplits a large story after slice-plan refinement into smaller stories and mapped slice plans. Use when resplitting is requested, including after a more-than-15-slices recommendation. Leaves the first story and plan refined; later plans await story refinement and backlog priorities are reconsidered.
dough-story-decomposition
by terryyin
Challenges and decomposes a broad product problem into ordered Valuable/Visible/Vertical stories with rough effort hypotheses. Use when the parent problem, candidate stories, or learning priority are unresolved. Writes one non-executable seed.
dough-story-refinement
by terryyin
Clarifies selected stories before execution planning by establishing goal, scope, and key examples in each story's seed. Adds UI or architectural detail only when needed. Use for selected-story refinement, not broad problem decomposition, candidate selection, or slice sizing.
release-version
by terryyin
Prepare or finalize an Open Dough source release with VERSION, CHANGELOG.md, and a matching Git tag. Use when the user asks to release-version, prepare or finalize a release, write VERSION or CHANGELOG, or create a version tag.
extract-guidance
by terryyin
Turn one supplied project skill or rule into a Proposed, reusable Open Dough skill and recognition record without changing the source. Use when an Open Dough maintainer asks to extract, generalize, or make a project practice reusable.
unrelated-guidance
by terryyin
Fixture guidance outside ADR adoption.
other-host-guidance
by terryyin
Existing Claude Code guidance outside the selected Codex installation.
other-host-guidance
by terryyin
Existing Cursor guidance outside the selected Codex installation.
release-version
by terryyin
Prepare or finalize an Open Dough source release with VERSION, CHANGELOG.md, and a matching Git tag. Use when the user asks to release-version, prepare or finalize a release, write VERSION or CHANGELOG, or create a version tag.
acme-change-readiness
by terryyin
Review an Acme change proposal before implementation. Use when someone asks whether an Acme change is ready to build.