Applies the deterministic sanitizecheck confidentiality Govern gate after lesson-cluster, deciding from identifiers, personal data, commercial figures, licensed material, aggregation risk and a confidence floor whether each asset and lesson is held or a release candidate for human review (default HOLD). Use when asked…
Starts every Scenario 03 mobilization run, including a cold start: runs the deterministic scopedigest engine on the SOW, letter, pursuit record, confirmed roster and Scenario 02 staffing and reports only its output (never invents scope, dates or names; never sends, shares or provisions anything). Use when the user…
Matches released Scenario 01 Closeout knowledge to the engagement with the deterministic knowledgematch engine and reports only engine output (never invents assets, scores or summaries, and never publishes, sends or shares knowledge). Use when the user asks "what prior knowledge can the joiner use?", "which reusable…
Drafts this engagement's internal mobilization pack, joiner briefing and first-week plan only from the governed access-checklist.json and mobilization-pack.md, keeping every status, hold and DRAFT banner (never invents content, sends, shares or posts it). Use when the user asks "draft the onboarding pack from the…
Explains the engine-built team roster in scope.json: who is confirmed, who is only proposed by Scenario 02, and who is excluded or needs review, using only engine output (never invents names, adds anyone to a roster, sends or shares; conflict reasons stay confidential). Use when the user asks "who is on the team?"…
Applies the deterministic ethical-wall Govern gate and least-privilege access checklist for the joiner (wallcheck and accesschecklist engines) and owns every wall-status question, including claims that a wall was lifted, cleared or waived (never invents a status; never provisions access, grants a wall exception, sends…
Normalizes bench, availability, rate and conflicts-register data into benchcandidates[] and constraints[] after role-intake, keeping every record and its citation without deciding fit or eligibility. Use when the user says "check the bench", "who is available?", "pull the roster", "include rates" or "load the…
Applies staffing independence, conflict, prior-role (including prior client board service), ethical-wall and availability rules to fit-scored candidates and refuses ineligible ones; it never clears a conflict or grants an exception. Use when the user says "is anyone conflicted?", "can we staff them?", "check…
Computes deterministic, pre-governance candidate-role fit scores, utilisation context and provisional ranks with the bundled engines, after bench-query and before constraint-check. Use when the user says "rank the bench", "score the candidates", "who is the best fit?", "compare candidate fit for this role" or "show…
Reads a signed engagement, SOW role extract, mobilisation note or staffing request into the ps.engagement-staffing-bench-match.v1 staffing contract (engagement, client affiliates and roles, each field cited) as the first step of every staffing slate. Use when the user says "new engagement signed", "staff this SOW"…
Drafts the partner-ready staffing recommendation from constraint-check output (eligible slate, refused top matches, conflicts, utilisation context and gap statements); it is draft only and never sends, assigns or approves, and partner notes built from constraint-check output stay with slate-draft. Use when the user…
2-3 sentences describing what this project does, who it's for, and what problem it solves. Helps the AI understand the domain and make appropriate design decisions.
2-3 sentences describing what this project does, who it's for, and what problem it solves. Helps Cascade understand the domain and make appropriate design decisions.
How to model background work, step functions, and polling - use this skill when testing async workflows, job queues, or operations that complete in the background.
How to test for race conditions using concurrent tests and linearizability - use this skill when testing concurrent operations or finding race condition bugs.
Testing systems not written in .NET - trace-based conformance testing, JSON test plan export, and executing from any language. Use when the user's system is in Python, Go, Java, Rust, C++, or any non-.NET language, or when they ask about trace validation or exporting test cases.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: