terryyin
- 16 skills
- 0 followers
- 8 hours ago last updated
- ▌ Post Change Refactor · terryyinRefactor and clean up the uncommitted change before committing. Eliminate duplication, rename unclear domain concepts, collapse shotgun surgery when another similar change is likely, remove dead / test-only / redundant code, split files larger than 250 lines into cohesive modules, and confirm related tests still pass. Use after finishing a phase or sub-phase and before commit, or whenever the developer asks to clean up the current change. Triggers on: refactor change, clean up change, post-change refactor, before commit cleanup, tidy current change.
- ▌ Bug Fixing · terryyinFix bugs with a test-first workflow. Use when the user reports a bug, asks to fix a defect, or describes unexpected behavior. Triggers on: bug, fix, defect, broken, regression, not working, unexpected behavior.
- ▌ Phased Planning · terryyinDecompose tasks into phased plans with one behavior per phase. Use when planning new features, breaking down large tasks, when a task has been in progress for over 10 minutes, or when the planning timer hook fires. Triggers on: plan, decompose, phases, break down, task too large, stuck.
- ▌ Tty Assert Release · terryyinPrepares an npm release for tty-assert: edits CHANGELOG.md and package.json, verifies lint/test/build, commits, tags vX.Y.Z, and pushes branch plus tag to trigger GitHub Actions Release. Use when the user asks to release, publish to npm, ship a version, cut a tag, or bump the package version for tty-assert.
- ▌ Dough Story Wrap Up · terryyinCloses one completed story after plan execution and retrospective. Assimilates lasting product knowledge, removes that story's spent plan and history so Git can recover it, and reports truthfully when required inputs are missing or unfinished. Use to wrap up a story, close a completed story, or delete spent plan and execution history after retrospective.
- ▌ Dough Execution Retrospective · terryyinReviews one completed or in-progress plan execution against its original story, aggregate commit set, current whole-product architecture, and test suite. 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, record supported process findings in `DearDough.md`, and recommend product work; never implements them.
- ▌ Dough Update · terryyin bundleApply 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 Execute Plan · terryyin bundleExecutes 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 Adr Awareness · terryyinUse 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 Resplit Story · terryyinResplits 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 Slice Planning · terryyinPlans 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 Product Backlog · terryyinMaintains and reprioritizes a product backlog list of story references. Use to add, reorder, or complete backlog items. Excludes classroom and workshop exercise backlogs.
- ▌ Dough Story Refinement · terryyin bundleClarifies 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 Story Decomposition · terryyin bundleChallenges 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 Post Change Refactor · terryyin bundleRefactors 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 Slice Plan Refinement · terryyinRefines 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.