CopilotAtelier.psd1
|
@{ RootModule = 'CopilotAtelier.psm1' # Replaced at build time by GitVersion. ModuleVersion = '3.1.0' GUID = '67bbef0b-f4de-4c1b-bb5a-b34104beb5b7' Author = 'raandree' CompanyName = 'raandree' Copyright = '(c) raandree. All rights reserved.' Description = 'Portable GitHub Copilot customization library. Ships custom agents, auto-applied instructions, on-demand skills, prompt templates, and lifecycle hooks, and installs them into the well-known ~/.copilot discovery folders that VS Code, the GitHub Copilot CLI, and Claude Code read.' PowerShellVersion = '5.1' FunctionsToExport = @('Get-CopilotAtelierVersion','Install-CopilotAtelier','Update-CopilotAtelier') CmdletsToExport = @() VariablesToExport = @() AliasesToExport = @() PrivateData = @{ PSData = @{ Tags = @( 'Copilot' 'GitHubCopilot' 'VSCode' 'Agents' 'Skills' 'Prompts' 'Instructions' 'Hooks' 'AI' 'Windows' 'Linux' 'MacOS' ) LicenseUri = 'https://github.com/raandree/CopilotAtelier/blob/main/LICENSE' ProjectUri = 'https://github.com/raandree/CopilotAtelier' IconUri = 'https://raw.githubusercontent.com/raandree/CopilotAtelier/main/assets/CA-glyph-on-light.png' Prerelease = 'preview0003' ReleaseNotes = '## [3.1.0-preview0003] - 2026-08-05 ### Added - **New Prompt `audit-case-file`** (2026-08-05). A drafting session accumulates conclusions, and over a long-running matter those conclusions migrate from summary to summary until they read like established fact. The empirical trigger was a single session on a live case file in which three assertions were checked against the primary corpus for the first time: one was refuted by a message the author had sent himself, one had been framed backwards by the assistant and was in truth the strongest argument available, and one was correct in substance but attackable in its wording against the exact phrase a third party had used. None of the three was careless. All three had survived because nobody had opened the source file since the claim was first written down. The Prompt exists to open them. Its load-bearing rule is that **the project memory is a finding aid and not evidence** — a claim resting only on the Memory Bank or on a prior work product counts as unsupported until traced to an unaltered primary document or a reproducible system value. The second rule is procedural and equally decisive: **run it in a fresh session**, because an agent that drafted the material carries its own conclusions in context and will confirm them, which is precisely the failure the audit exists to catch. Author and addressee are treated as part of every claim, since a quote attributed to the wrong person or a letter said to have been addressed to the reader when it went to someone else is a Blocker rather than a detail. Six error classes are hunted rather than awaited, each drawn from an observed failure: claims about one''s own earlier knowledge that the author''s own outbox refutes; misattribution; drifting figures, for which a value history is built and the one currently valid value named; reference periods that cut across each other, where the project''s period definition must be established rather than assumed; third-party system evidence held only as a screenshot or a link, since a link is not preservation; and asserted deadlines with no traceable source. Work is ordered by deadline — ready-to-send drafts with a running clock complete before the case file itself — so a slow audit cannot cost a dispatch date. The Prompt is read-only by construction: no edits, no wording suggestions, no dispatch, and "not found" is an explicit valid finding so a missing source cannot be papered over with an invented one. Built as a Prompt rather than a Skill because it is a deliberately invoked workflow with a fixed procedure and a single artefact, the direct analogue of [`peer-review.prompt.md`](Prompts/peer-review.prompt.md), and because a Skill covering claim-to-source verification would overlap [`citation-integrity`](Skills/citation-integrity/SKILL.md) and degrade auto-selection for both. It orchestrates `citation-integrity`, `devils-advocate-review`, and the severity labels of `code-review-and-quality` instead of restating them. Folder roles are derived from the Memory Bank routing table at run time rather than hard-coded, so the Prompt carries no project-specific paths, route names, or facts and applies to any matter that keeps primary sources apart from its own work products. Prompt count 10 → 11. - **New Skill `gilb-requirements-engineering`** (2026-08-04). Nothing in the library covered Tom and Kai Gilb''s method, and the nearest neighbour was not a substitute: [`grill-me`](Skills/grill-me/SKILL.md) is Brooks-derived and deliberately qualitative, so "the portal must be significantly faster" survives its twelve-category interview intact and reaches the Design Concept as prose. The new Skill is the counterpart that refuses it. Its single rule is that a quality requirement without a `Scale`, a `Meter`, and a numeric level is a wish with a noun in it, and the nine-step protocol enforces the consequences. **Sort every sentence into function, quality, resource, design, or condition and evict the design**, because a requirement that names a technology has pre-empted the decision it was supposed to inform. **State the benchmarks `Past`, `Record`, and `Trend` before any target**, since `Past` and `Goal` together define the 0–100 % span the Impact Estimation Table computes against, and a `Goal` written without a `Past` leaves the table uncomputable. **Keep `Fail` and `Survival` separate from `Goal`**, so a missed ambition stops reading like an incident and the signal survives. Every number carries a `Source` or an explicit `<TBD>`, because an invented benchmark is indistinguishable from a measured one six months later. Four references keep the body at 322 lines. [`planguage-keywords.md`](Skills/gilb-requirements-engineering/references/planguage-keywords.md) carries the keyword set, the `[qualifier]` syntax that collapses five copy-pasted requirements into one, and the eight specification errors that recur. [`impact-estimation.md`](Skills/gilb-requirements-engineering/references/impact-estimation.md) carries the table arithmetic and the 0.0–1.0 credibility scale, whose whole point is that a 90 % impact at credibility 0.2 loses to a 40 % impact at credibility 0.7 — the method systematically prefers what is known to work over what would be spectacular if it worked, and it surfaces negative cells that prose comparisons almost never do. [`evo-planning.md`](Skills/gilb-requirements-engineering/references/evo-planning.md) carries the roughly 2 %-of-budget step size, the three tests that separate a step from a task, the backroom/frontroom split that prevents delivery theatre, and the estimate-versus-actual feedback teams drop — which is exactly what turns Evo back into ordinary incremental delivery. [`spec-quality-control.md`](Skills/gilb-requirements-engineering/references/spec-quality-control.md) carries the 300-word logical page, the roughly one-page-per-hour checking rate that makes sampling mandatory, the ÷0.3 detection-effectiveness correction whose omission understates density threefold, and the ≤ 1.0 majors-per-page exit criterion with the finding that a failing specification is returned to its author rather than reviewed harder. Built as a Skill rather than a Custom agent because the knowledge is portable across harnesses and auto-triggers from every agent, where a persona has to be selected and pins a model priority array. `grill-me` now cross-references it on both sides of the overlap audit, so elicitation hands off to quantification instead of competing with it. Skill count 43 → 44. - **New Skill `german-tax-research`** (2026-07-31). The `tax-researcher` agent had instructed itself to "load **german-tax-research**" since the day it was written, and no such Skill existed — every income tax session therefore ran on whatever the model happened to recall about the EStG and the AO. The Skill closes that dangling reference and carries the material that a multi-year `Einspruchsverfahren` produced. Three rules in it are the ones that repeatedly decided outcomes. **Four proof types, judged separately**: an invoice evidences the cost and nothing else, so payment, professional purpose or participation, and the absence of third-party reimbursement each need their own document, and a missing one is closed with a signed `Eigenbeleg` or the position is dropped — never carried silently into the letter. **Reconcile against the transmitted return, not the workbook**: a control table with transmitted, evidenced, difference, and treatment per position is the only instrument that catches an allocation key a spreadsheet quietly "improved" away from the one the tax office applied, a bank credit that is a net figure hiding a gross receipt plus a disbursement, and a byte-identical invoice claimed in two different years. **Disclose every difference in the point it belongs to**, including corrections against the taxpayer''s own interest, because `§ 153 Abs. 1 AO` obliges notification once an error is known and an examiner who sees a self-reported correction reads the rest of the package differently. The Skill also fixes the deadline arithmetic that is wrong in most self-prepared objections: notification is deemed on the **fourth** day after dispatch since the PostModG took effect on 1 January 2025, not the third, and both that day and the end of the one-month objection period shift over weekends and state public holidays under `§ 108 Abs. 3 AO`. [`scripts/Get-SteuerFrist.ps1`](Skills/german-tax-research/scripts/Get-SteuerFrist.ps1) computes it, selects the three- or four-day fiction from the dispatch date, and reports every shift it applied together with the holiday set of the state where the Finanzamt sits. Six references keep the body inside the progressive-disclosure budget: [`fristen-und-verfahren.md`](Skills/german-tax-research/references/fristen-und-verfahren.md) for notification, objection, AdV, estimation, surcharges, interest, limitation, and competence; [`vermietung-und-afa.md`](Skills/german-tax-research/references/vermietung-und-afa.md) for `Anlage V`, the AfA rates including the 5 % declining balance of `§ 7 Abs. 5a EStG`, the purchase-price split after BFH IX R 26/19, and the handling of a `§ 7i` certificate as an outstanding `Grundlagenbescheid`; [`werbungskosten-und-abzuege.md`](Skills/german-tax-research/references/werbungskosten-und-abzuege.md); [`belegaufforderung-antwort.md`](Skills/german-tax-research/references/belegaufforderung-antwort.md) with the end-to-end answer procedure, the residence and centre-of-life evidence order, and the dispatch channels that actually prove receipt; [`kennzahlen.md`](Skills/german-tax-research/references/kennzahlen.md) with amounts and filing deadlines per assessment period 2021 to 2026, including the `§ 36 EGAO` extensions that make the 2020 to 2024 dates non-obvious; and [`vorlagen.md`](Skills/german-tax-research/references/vorlagen.md) with the German letter templates. Cross-referenced with `evidence-package-assembly`, which builds the `Anlage` PDF this Sk' } } } |