AI SummaryYou are helping an enterprise architect generate French public procurement documentation (Dossier de Consultation des Entreprises) aligned with the Code de la Commande Publique, UGAP, and DINUM digital doctrine requirements. Identify the target project from the hook context. If the project doesn't e
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "arckit-fr-marche-public" skill in my project. Please run this command in my terminal: # Install skill into your project (2 files) mkdir -p .claude/skills/arckit-fr-marche-public && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/arckit-fr-marche-public/SKILL.md "https://raw.githubusercontent.com/tractorjuice/arc-kit/main/arckit-codex/skills/arckit-fr-marche-public/SKILL.md" && mkdir -p .claude/skills/arckit-fr-marche-public/agents && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/arckit-fr-marche-public/agents/openai.yaml "https://raw.githubusercontent.com/tractorjuice/arc-kit/main/arckit-codex/skills/arckit-fr-marche-public/agents/openai.yaml" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
[COMMUNITY] Generate French public procurement documentation aligned with code de la commande publique, UGAP catalogue, and DINUM digital standards
User Input
`text $ARGUMENTS `
Instructions
> Note: Before generating, scan projects/ for existing project directories. For each project, list all ARC-*.md artifacts, check external/ for reference documents, and check 000-global/ for cross-project policies. If no external docs exist but they would improve output, ask the user.
Step 0: Read existing artifacts from the project context
MANDATORY (warn if missing): • REQ (Requirements) — Extract: functional requirements (FR-xxx) for procurement scope, non-functional requirements (NFR-xxx), integration requirements (INT-xxx), data sovereignty and security requirements • If missing: warn that procurement documentation requires defined requirements to produce a valid requirements statement RECOMMENDED (read if available, note if missing): • RISK (Risk Register) — Extract: vendor risks, technology risks, lock-in risks, sovereignty risks • SECNUM (SecNumCloud Assessment) — Extract: cloud qualification requirements, recommended providers, data classification that drives sovereignty clauses • DINUM (DINUM Standards Assessment) — Extract: mandatory DINUM standards (RGAA, RGS, RGI) to include as contract requirements OPTIONAL (read if available, skip silently): • PRIN (Architecture Principles, 000-global) — Extract: open source policy, cloud strategy, technology standards • DATA (Data Model) — Extract: data categories (health data → HDS clause, personal data → GDPR/DPA clause)
Step 0b: Read external documents and policies
• Read any external documents in external/ — extract previous procurement files, UGAP framework references, legal notices, budget documents • Read any global policies in 000-global/policies/ — extract procurement policy, open source policy, data classification policy • If procurement-related external documents found, use them to pre-populate threshold analysis and budget constraints.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster