{"id":44227,"plugin_id":"plugin_asdk_app_6a958f23ec408191a845944d93e24925","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:15:25.461Z","digest":"ac4e3ca32088ae71984b1a622b440f51a3e44ff3fe805c94e4959443f0ef0377","against":null,"payload":{"description":"Instruct a type of structure in a Stratta dossier (a bored pile, a retaining wall, a slope, a raft) by opening the questions it raises from the office's template or from the norm's own chapters, then gathering the clauses each one rests on, stopping short of any decision. Trigger phrases: \"instruis\", \"prepare les questions pour\", \"checklist pour\", \"instruct the pile\", \"what do we need to settle for\".","included_files":[],"name":"instruct-structure","skill_md_contents":"---\nname: instruct-structure\ndescription: Instruct a type of structure in a Stratta dossier (a bored pile, a retaining wall, a slope, a raft) by opening the questions it raises from the office's template or from the norm's own chapters, then gathering the clauses each one rests on, stopping short of any decision. Trigger phrases: \"instruis\", \"prepare les questions pour\", \"checklist pour\", \"instruct the pile\", \"what do we need to settle for\".\n---\n\n# Instruct a type of structure\n\nUse this skill when the user starts on a type of structure and wants the questions it\nraises laid out with the clauses that govern them, before deciding anything: \"instruis\nle pieu P38\", \"qu'est-ce qu'on doit trancher pour ce mur de soutenement\".\n\nDo not use it to answer one technical question (that is the ordinary method) and do not\nrecord decisions with it: it prepares the work, the engineer decides.\n\n## Steps\n\n1. `list_dossiers` then `load_dossier` (or `open_dossier` when the project is new). If\n   questions already cover the structure, do not open them twice: list what exists first.\n2. `list_templates`. When a template matches the type of structure, `apply_template`: it\n   opens the questions with the clauses they rest on and says which clauses the corpus\n   lacks. Report both to the user and stop here unless the user asks for more.\n3. Without a template: `get_toc` on the norm that governs the structure (SIA 267 for\n   geotechnics, SIA 262 for concrete, and so on, only if `list_norms` holds it), then\n   `get_subtree` on the chapter of the structure. Propose the questions, one per thing to\n   settle, in the user's words (\"Quel angle de frottement retenir pour la moraine ?\",\n   \"Le pieu peut-il etre conserve ?\"), and open them with `open_question` after the user\n   agreed on the list. Name the options when the chapter offers several methods.\n4. For each question, read the clauses that govern it (`get_section`, follow resolvable\n   references) and file each as a `reference` with `save_finding`: the clause, its page,\n   its edition, one clause per call.\n5. Summarise: the questions opened, the clauses filed, what the corpus does not hold, and\n   which question the user wants to work on first.\n\n## Rules\n\n- Open questions only with the user's agreement on the list; ten precise questions beat\n  one that bundles them.\n- File clauses you read in this conversation, never from memory.\n- Do not write a hypothesis, an observation or a decision here. The office may have its\n  own `instruct-structure` skill (`list_skills`): it replaces this one.\n\n## Example\n\nUser: \"instruis le mur de soutenement de la villa Morges\". Agent: loads the dossier, finds\nno template, reads the SIA 267 chapter on retaining structures, proposes six questions\n(earth pressure model, drainage, bearing capacity of the base, sliding, overturning,\nserviceability), opens them once the user agrees, files nine clauses, and reports that\nthe corpus does not hold the SIA 261 clause on traffic loads behind the wall.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}