pair-change

Files (1)

• SKILL.md

SKILL.md (first lines)

Follow `~/.agents/sdlc/READING.md`; reuse required documents already read in
full, unchanged and retained in context. A skill transition does not reload them.

Read `~/.agents/sdlc/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 `~/.agents/sdlc/ORG-SCHEMA.md` and run
`~/.agents/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 `~/.agents/sdlc/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.

From tigger-developer/sdlc, Apache-2.0.

More from tigger-developer/sdlc