Feature outcome lens

Use this skill when the first independently verifiable outcome is a new supported capability or externally observable behavior. It is not a fixed feature workflow.

Receive from /cs when available: task id, risk, session key, passive observation run id and invocation-specific write constraint. A direct invocation must initialize/resume the same control state rather than create phase files.

Control contract

• Owner chooses the order of inspection, experiments, implementation and tests.
• Harness owns allowed writes, risk escalation, evidence recording and completion.
• Reviewer challenges omitted scope, regressions, weak acceptance evidence and duplicate paths.
• Actions inspect, propose, execute, verify, learn may repeat or be skipped when the current risk/evidence state permits.

Read only the relevant guide: