Poland Case Planning
Use for a multi-step administrative case, deadline orientation, evidence-category
planning, or a handoff between the user, an authority, and a professional. Keep
the plan transient: this skill does not create, update, or validate case files,
profiles, ledgers, or other durable user records.
Workflow
- State the abstract goal, citizenship/status category, locality category,
deadline owner, and unresolved non-identifying facts.
- Route the scenario and build the first checklist with the bundled CLI.
- Separate tasks into
verify, prepare, official-page handoff, and done.
- Attach a source ID to every deadline or material procedural statement.
- Return source evidence in the current response only: time, source ID, result,
locator, supported claim IDs, and optional content hash.
- Re-route after a status, job, family, locality, or official-letter change.
Never place PESEL, passport/document numbers, names, addresses, email, phone,
credentials, bank data, scans, correspondence, or personal-record content in
bundled plugin tools or a durable plan. A caller-owned tool may inspect the
minimum relevant personal material after explicit task-scoped authorization,
but the plan stays abstract and transient. The user may copy the generic output
into storage they control without further plugin access.
For the data and effect boundaries, read
../../references/operating-contract.md. For a domain procedure, hand off to its
focused skill; this skill owns transient planning, not eligibility or execution.
Scenario stop_before values are pause-and-classify checkpoints: resolve them
through ../../references/automation-playbook.md rather than treating every
listed external effect as permanently prohibited.
1---2name: poland-case-planning3description: Case planning. Use when Poland deadlines and multi-step procedures need a transient plan.4---56# Poland Case Planning78Use for a multi-step administrative case, deadline orientation, evidence-category9planning, or a handoff between the user, an authority, and a professional. Keep10the plan transient: this skill does not create, update, or validate case files,11profiles, ledgers, or other durable user records.1213## Workflow14151. State the abstract goal, citizenship/status category, locality category,16 deadline owner, and unresolved non-identifying facts.172. Route the scenario and build the first checklist with the bundled CLI.183. Separate tasks into `verify`, `prepare`, `official-page handoff`, and `done`.194. Attach a source ID to every deadline or material procedural statement.205. Return source evidence in the current response only: time, source ID, result,21 locator, supported claim IDs, and optional content hash.226. Re-route after a status, job, family, locality, or official-letter change.2324Never place PESEL, passport/document numbers, names, addresses, email, phone,25credentials, bank data, scans, correspondence, or personal-record content in26bundled plugin tools or a durable plan. A caller-owned tool may inspect the27minimum relevant personal material after explicit task-scoped authorization,28but the plan stays abstract and transient. The user may copy the generic output29into storage they control without further plugin access.3031For the data and effect boundaries, read32`../../references/operating-contract.md`. For a domain procedure, hand off to its33focused skill; this skill owns transient planning, not eligibility or execution.34Scenario `stop_before` values are pause-and-classify checkpoints: resolve them35through `../../references/automation-playbook.md` rather than treating every36listed external effect as permanently prohibited.
Xopoko