terryyin
@terryyin
Public Skills
reconcile-retrospective-findings
by terryyin
Reconciles supplied retrospective findings under stable internal Open Dough codes (ODF-NNN) and retains their evidence for later triage. Use when a maintainer asks to reconcile findings, retain supplied DearDough feedback, recommend a rename, assign an ODF code, or match source and internal finding names.
dough-maintain-findings
by terryyin
Adopts supplied, approved DD-NNN to ODF-NNN finding-name mappings in this project's DearDough.md while preserving evidence and former-code traceability. Use only on explicit skill invocation or an explicit request to adopt or rename finding codes; encountering findings or mapping recommendations does not authorize maintenance. Other finding cleanup and status changes are out of scope.
dough-pfe
by terryyin
Finds and assesses existing solutions across the whole product before an implementation responsibility is added or relocated. Use for PFE, Proudly Found Elsewhere, or when deciding whether to reuse, change, modularize, or replace an existing product solution.
triage-retrospective-findings
by terryyin
Recommend an ordered, evidence-linked follow-up proposal for reconciled Open Dough process findings, and when a developer selects a proposal, record one evaluable story in a suitable existing seed or a newly created canonical seed, queue its canonical reference, and link the retained finding. On later triage or rereview, surface existing queued or Taken follow-up with usable story and queue links instead of duplicating it. When a developer explicitly chooses to defer, seek more evidence, or retain current behavior, record that disposition on the finding without queueing a fix. Use when a maintainer asks to triage findings, prioritize process findings, recommend finding follow-up, rereview already-linked findings, queue a selected finding response, turn a selected retrospective finding into backlog work, defer a finding, request more evidence, or record no-change.
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-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.
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.
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.
unrelated-guidance
by terryyin
Fixture guidance outside ADR adoption.
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.