mainframe-record-project-problem

Record a project problem

Operate in the current project: the repository named by the task or, absent that, the active working repository. An explicit request to use this skill means apply the recording method there. Keep discovery and ticket writes inside that project and its explicitly configured issue routes.

Use this skill when work exposes a concrete problem in the receiving project and resolving it is outside the assigned result. Preserve the finding without silently expanding scope, then continue the assigned work when the problem does not prevent a valid or safe result.

First decide whether the problem belongs to the active work. If it prevents achieving or verifying the assigned result, return it to that work instead of deferring it to a ticket. Do not use a ticket to make unfinished in-scope work appear complete.

When the work will deliberately leave an evidenced problem unresolved, read references/surface-ticket.md and apply its surfacing boundary before recording or returning the finding.

If no concrete project finding exists yet, keep this method ready for the assigned work; do not fabricate tickets or start a random search campaign.

Use the project's queue

When the project uses docs/tickets/AGENTS.md, read that contract and create observations with its required YAML fields and Evidence section. Preserve matching open records; recording does not perform campaign investigation or lifecycle transitions.

Otherwise inspect only the current project's effective instructions and configured issue locations. Honor an established local queue or external tracker; do not establish a competing source of truth. Existing noncanonical tickets require the explicit mainframe-tickets-init migration workflow, not silent normalization by this skill.

If no issue route exists and local documentation writes are authorized, establish docs/tickets/ using references/new-queue.md, then record the evidenced finding in open/observations/. An explicit request to apply this skill authorizes this local setup unless the task or project forbids it; automatic use stays within existing write authority. Create the rule files and directories, not an audit campaign or artificial records. Preserve the project's tracked/ignored ownership and do not change ignore rules without a settled choice.