tractorjuice

[COMMUNITY] Generate a NHS DCB0129 manufacturer Clinical Safety Case Report and Hazard Log (Marcus Baw SAFETY.md 3-file spec) for a digital health product placed on the NHS market.

[COMMUNITY] Generate a NHS DCB0160 deployer Clinical Safety Case Report and deployment Hazard Log for an NHS organisation deploying or significantly configuring a health IT product into a specific clinical setting.

Document architectural decisions with options analysis and traceability

Design AI agent architecture — patterns, tool contracts, memory, orchestration, guardrails

Design AI agent governance — oversight models, approval workflows, audit requirements, compliance mapping

Assess AI agent program maturity across design, governance, security, integration, and operations

Design AI agent security — sandboxing, permissions, injection defences, output validation

Assess UK Government AI Playbook compliance for responsible AI deployment

This skill should be used when the user wants to bulk-build ArcKit artefacts in parallel rather than running individual /arckit:* commands one at a time. Invoke manually with /arckit:arckit-build when the task sounds like 'kick off a build', 'build everything', 'generate all artefacts', 'run all the commands', 'rebuild this project from scratch', 'resume the build', 'pick up where we left off', 'refresh the artefacts', 'run the recipe', 'build the whole project end-to-end', or 'parallel build', or mentions `--plan`, `--resume`, `--target`, `--refresh`, `--recipe`, or `.arckit/state.json`. The skill orchestrates parallel /arckit:* generation using subagent isolation: reads project state, computes the artefact dependency DAG, dispatches one subagent per target per wave (each subagent invokes a /arckit:* skill in its own context), validates outputs, commits the wave, and persists progress to .arckit/state.json for resumability.

This skill should be used when the user asks about "ISO 27001", "Cyber Essentials", "NCSC principles", "cloud security", "what certifications", "SOC 2", "data protection", "UK GDPR", "security clearance", "PCI DSS", "compliance framework", "CSA STAR", "DSPT", "Technology Code of Practice", "AI Playbook", "what evidence do I need", "security certification", "NHS data", "BPSS", "SC clearance", "DV clearance", "what security do I need", "certification cost", "ISO 22301", or needs guidance on security certifications, compliance requirements, and evidence for G-Cloud submissions.

This skill should be used when the user asks about "character limit", "how many features", "what lots", "CCS questions", "service categories", "declaration questions", "word limit", "mandatory exclusion", "service name limit", "pricing format", "what questions does CCS ask", "lot 1 categories", "lot 2 categories", "lot 3 categories", "how many words", "features limit", "benefits limit", "service description limit", "framework questions", "marketplace questions", "G-Cloud question structure", or needs quick lookups on Digital Marketplace field constraints and lot structures.

This skill should be used when the user asks about "SFIA level", "SFIA skills", "day rate", "what level is", "solution architect level", "Lot 3 roles", "DDaT roles", "AI skills framework", "cloud migration roles", "consultancy rates", "SFIA mapping", "role to SFIA", "skill level", "cloud support roles", "what SFIA level", "rate card", "SFIA 8", "junior consultant rate", "senior consultant rate", "principal consultant", "DevOps engineer level", "security engineer level", "project manager SFIA", or needs guidance on SFIA levels, role mappings, day rates, and Lot 3 service team compositions.

Cut a new ArcKit release — bump versions in lockstep, regenerate non-Claude formats, validate plugin/marketplace agreement, tag, and push to standalone repos. Use when the user says 'cut a release', 'release ArcKit', 'ship vX.Y.Z', 'bump the version and release', 'do the release flow', 'tag and publish', or 'push the extensions'. This is a manual, high-consequence workflow: it never runs automatically.

Use when reviewing a PR to tractorjuice/arc-kit that adds or extends a community jurisdictional overlay (e.g. au-*, ca-*, uae-*, fr-*, at-*, eu-*, future state-level like au-vic-*) — produces a structured review with blockers, important issues, minor issues, and positive callouts.

This skill should be used when a new ArcKit command has been added and documentation needs updating across the repository. Triggers: update documentation for new command, update command count, add command to README, update DEPENDENCY-MATRIX, update docs/index.html, new command documentation checklist, update all docs for new command, add command to dependency matrix, update command tables, sync documentation after adding command, I added a new command what do I update, post-command documentation, new slash command docs.

This skill should be used when the user is starting an architecture project or asking what to run next. Load whenever the task sounds like 'I'm starting a new project', 'guide me through', 'what command should I run', 'what comes next', 'how do I begin', 'help me get started', 'which /arckit:* in what order', 'set up a new project', 'new system build', or 'where do I start'. Recommends a tailored command sequence based on sector, project type, current stage, and timeline.

Generate a Wardley Map from a scenario description using a formal mathematical model. Produces OWM-format output (with an optional Mermaid wardley-beta block for GitHub rendering) and strategic analysis grounded in Wardley's cheat sheet, 61 gameplays, and 40 doctrine principles. Use this skill whenever the user asks for strategic reasoning about the components of a business, product, or system — specifically when they mention any of value chain, strategic positioning, competitive landscape, strategic moat, component evolution, genesis-to-commodity spectrum, build-vs-buy across multiple components, where to invest engineering effort, what to commoditise or outsource, mapping a business or platform or marketplace strategically, or explicitly "Wardley map". Always trigger when "Wardley" appears in the request. Also trigger when the user describes a business or system and asks about strategic roadmap, moats, or board-level positioning — even without naming the framework. Skip for flowcharts, UX journey maps, proc

Create strategic Wardley Maps for architecture decisions and build vs buy analysis

Decompose user needs into value chains for Wardley Mapping

Generate Wardley Maps in the WTG2 domain-specific language. Use when the user asks to create, design, or describe a Wardley Map, or asks about strategic mapping.

This skill should be used when the user asks about Wardley Mapping, evolution stages, strategic positioning, creating maps, value chain decomposition, gameplay patterns, doctrine assessment, climatic patterns, build vs. buy, or inertia analysis.

Generate a Wardley Map from a scenario description using a formal mathematical model. Produces OWM-format output and strategic analysis grounded in Wardley's cheat sheet, 61 gameplays, and 40 doctrine principles. Use when the user wants a Wardley Map of a system, business, or domain, or asks to "map" something strategically.

This skill should be used when the user is starting an architecture project or asking what to run next. Load whenever the task sounds like 'I'm starting a new project', 'guide me through', 'what command should I run', 'what comes next', 'how do I begin', 'help me get started', 'which /arckit:* in what order', 'set up a new project', 'new system build', or 'where do I start'. Recommends a tailored command sequence based on sector, project type, current stage, and timeline.

This skill should be used when the user asks about Mermaid diagram syntax, how to write flowchart, sequence, class, state, ER, Gantt, C4, mindmap, timeline, or other diagram types, node shapes, styling, theming, or rendering errors.

This skill should be used when the user asks about PlantUML syntax for C4-PlantUML, sequence, class, activity, state, ER, component, deployment, or use case diagrams, rendering errors, layout conflicts, skinparams, or themes.

This skill should be used when the user asks about Wardley Mapping, evolution stages, strategic positioning, creating maps, value chain decomposition, gameplay patterns, doctrine assessment, climatic patterns, build vs. buy, or inertia analysis.