pair-change
Run explicitly selected paired development with live operator validation and lean closure records.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- pair-change
- description
- Run explicitly selected paired development with live operator validation and lean closure records.
03 SKILL.md 正文
Follow /opt/sdlc/docs/READING.md; reuse required documents already read in
full, unchanged and retained in context. A skill transition does not reload them.
Read /opt/sdlc/docs/MAIN.md and PAIRING.md, then the project profile and
applicable standards. The operator's bounded objective and explicit iteration
instructions are the working specification. A question remains a question.
For code or script changes, reuse the applicable work item or create its skeleton
on primary before coding, reserving any new ID under DELIVERY.md. Only then
select the implementation branch; paired admission does not require advance
definition sign-off. Append authorized requirements and decisions as the session
progresses. Documentation-only changes do not require a ticket.
Iterate implementation with the operator. Use automated TDD wherever justified,
and record each explicit visual, ergonomic, editorial, or operational validation
without replacing it with artificial automation. Audit each coherent code
increment promptly with code-audit in this session, not each keystroke.
Before that review, follow /opt/sdlc/docs/ORG-SCHEMA.md and run
/opt/sdlc/bin/sdlc-validate --help, then its delivery-code readiness check.
Every AT/RT/OT must be GREEN; record outstanding UTs as AMBER. This route does not
require a pre-build test-code audit.
Update affected product documentation before that final delivery verdict; do not
require a polished retrospective specification before reviewing the code increment.
When the outcome stabilizes, consolidate spec.org, validation.org, and
affected documentation, then run the retrospective definition review.
Use definition-audit in this session for the retrospective definition review.
Follow /opt/sdlc/docs/AUDITS.md for internal evidence and continuation. Refer proposed behaviour
or design changes to the operator for normal delivery; do not redesign during
wrap-up. Ask the operator to confirm the recorded user tests and close the work.
Review orchestration and evidence ownership follow AUDITS.md; current-session
review uses SELF-AUDIT.md. No external call or new reviewer is authorized.
04 同仓库更多 Skills
useful-be
Load the minimum project and engineering context needed for useful work.
test-code-audit
Self-review written tests before implementation in the current author context; never launch or act as an independent auditor.
summarize-issues
Summarize a project's open work against its specifications and architecture. Advisory only; no file changes.
recommendations-please
Provide concrete expert recommendations for a technical decision without making file changes.
migrate-legacy-acs-to-sdlc-v1
Archive and close a brownfield project's legacy GitHub tickets while reconciling its SDLC v1 acceptance-criteria ledger and documentation before SDLC v3 initialization. Invoke only when the operator requests this migration.
hands-off-spike
Run an explicitly invoked, unattended exploratory spike from a signed-off brief, with current-session internal test-code and implementation reviews, never merged or deployed.