shadow-doc
Skill1 starsChanged yesterdayMITView on GitHub
Enterprise & Government SDLC Document Engineering. Use when generating or updating .docx, .pdf, .xlsx, or .csv deliverables from Canonical JSON AST v2.0 or .md sources, verifying citations with reference_verifier.py, or checking document traceability.
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- handoffSkill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-handoverSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-mobileSkill
- shadow-modernizeSkill
- shadow-monarchSkill
- shadow-observeSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-presalesSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-releaseSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-supplychainSkill
- shadow-testSkill
- shadow-uatSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 0 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill whenever the Monarch asks to create, import, selectively update, validate, trace, approve, render, or package formal SDLC, …
- Very specific: line 15
All text, tables, diagrams, and metadata changes MUST be applied to the Canonical JSON AST (.json) or Markdown source (.md) and regenerated …
- Very specific: line 17
Never invent dates, ticket IDs, metrics, stakeholder names, test results, or deployment topologies.
- Very specific: line 21
Document owner cannot self-approve (owner != approver), and HANDOVER / BAST artifacts cannot transition to APPROVED/RELEASED without signed …
- Very specific: line 25
All exports automatically redact leaked credentials ([REDACTED_SECRET]), reject cross-project forbidden_terms, and write files atomically …
- Very specific: line 29
Industry Standards First: Every SDLC document (SRS, SDD, RTM, TEST_PLAN, UAT, SECURITY_RISK, INCIDENT, MANUAL, MAINTENANCE) anchors to …
- Very specific: line 37
All 20 templates live in templates/ and are cataloged in TEMPLATE_CATALOG.md:
- Very specific: line 130
Word TOC Field Note: When opening generated .docx files in Microsoft Word, press Ctrl+A then F9 to populate dynamic page numbers in the …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Shadow Doc v2.0 (/shadow-doc) — Enterprise & Institutional SDLC Document Engineering System
Use this skill whenever the Monarch asks to create, import, selectively update, validate, trace, approve, render, or package formal SDLC, enterprise, or government documents (.docx, .pdf, .xlsx, .csv, .md, .json, .zip).
1. Non-Negotiable Golden Laws (v2.0 + v1.0 Hybrid)
- NEVER Edit Binary Outputs Directly (
.docx,.xlsx,.pdf):- All text, tables, diagrams, and metadata changes MUST be applied to the Canonical JSON AST (
.json) or Markdown source (.md) and regenerated viascripts/doc_scaffold.py.
- All text, tables, diagrams, and metadata changes MUST be applied to the Canonical JSON AST (
- Zero Fabricated Facts & Evidence-Backed Claims (
DOC-FR-012,DOC-FR-020,AT-09):- Never invent dates, ticket IDs, metrics, stakeholder names, test results, or deployment topologies. Unknown facts MUST remain explicit placeholders (
[ISI ...],[TBD],UNVERIFIED). - Any block claiming
PASS,APPROVED,DEPLOYED, orCLOSEDMUST cite a verifiedsource_refsentry. Strict validation (validate --strict) blocks release if unresolved placeholders or unverified claims exist.
- Never invent dates, ticket IDs, metrics, stakeholder names, test results, or deployment topologies. Unknown facts MUST remain explicit placeholders (
- Approved Document Protection & Separation of Duties (
DOC-FR-010,DOC-FR-011,AT-04,AT-11):- Documents in
APPROVEDorRELEASEDstatus are immutable in-place. Callingupdateon an approved document automatically forks a newDRAFTrevision (e.g.,1.1-DRAFT) withsupersedespointing to the approved revision. - Document
ownercannot self-approve (owner != approver), andHANDOVER/BASTartifacts cannot transition toAPPROVED/RELEASEDwithout signedevidence_ref.
- Documents in
- Selective Block Updates & Optimistic Concurrency (
DOC-FR-007,AT-03,AT-07):- Partial updates target a specific
scope_id(e.g.,FR-001) without mutating unrelated blocks, recordingbefore_hashandafter_hashinhistory[]. Concurrent edits with a staleexpected_hashfail closed (CONCURRENCY_CONFLICT).
- Partial updates target a specific
- Secret Scanning, Cross-Project Isolation & Atomic Rollback (
AT-06,AT-10,AT-14):- All exports automatically redact leaked credentials (
[REDACTED_SECRET]), reject cross-projectforbidden_terms, and write files atomically via.tmp+.bakrollback.
- All exports automatically redact leaked credentials (
- 100% v1.0 Backward Compatibility (
AT-12):- Legacy v1.0 commands (
--selftest,md-to-json,check-readiness) andbagian -> subbagian -> blokJSON files remain fully supported and can be migrated losslessly viamigrate-v1(preserving a.v1.bak.jsonbackup).
- Legacy v1.0 commands (
- Research & Normative Standards Source Policy (
NORMATIVE_STANDARDS_MAP):- Industry Standards First: Every SDLC document (
SRS,SDD,RTM,TEST_PLAN,UAT,SECURITY_RISK,INCIDENT,MANUAL,MAINTENANCE) anchors to authoritative standards (ISO/IEC/IEEE 29148:2018,ISO/IEC/IEEE 42010:2022,ISO/IEC/IEEE 29119,ISO/IEC 25010,NIST SSDF SP 800-218,OWASP ASVS 5.0.0,ISO/IEC/IEEE 12207,NIST SP 800-61,ISO/IEC/IEEE 14764,ISO/IEC/IEEE 26514) and official version-matched framework documentation (/context7MCP). - Academic Literature &
arXivPreprint Rules: Use peer-reviewed databases (IEEE Xplore,ACM Digital Library,SpringerLink,ScienceDirect, indexed viaSemantic Scholar/OpenAlex/Google Scholar) as supporting evidence when architectural or algorithmic decisions require empirical backing. Never default toarXivfor software engineering standards;arXivpreprints must be taggedsource_type: "PREPRINT"(peer_reviewed: false) unless a peer-reviewed journal/conference DOI is verified. - Mandatory Local Download & 7-Point File Safety Gate (
scripts/reference_verifier.py): Download publicly accessible reference files intodocs/references/and verify every downloaded or imported file withscripts/reference_verifier.py(checks extension allowlist, double-extension spoofing,%PDF-vsMZ/ELFmagic bytes, PDF/JavaScript&/Launchexploit tokens, HTML<script>injection, and SHA-256 manifest; unsafe files are immediately deleted from the local PC).
- Industry Standards First: Every SDLC document (
2. Catalog of 20 Standardized SDLC Templates (templates/01..20)
All 20 templates live in templates/ and are cataloged in TEMPLATE_CATALOG.md:
| # | Type Code | Template File | Document Title | Primary SDLC Stage | Collaborating Skill |
| 01 | SDLC_PLAN | 01_SDLC_PLAN.md | Software Development Lifecycle Plan | Discovery / Planning | /shadow-plan |
| 02 | BRD_PRD (PRD, BRD) | 02_BRD_PRD.md | Business and Product Requirements | Discovery | /shadow-discovery |
| 03 | SRS | 03_SRS.md | Software Requirements Specification | Discovery | /shadow-discovery |
| 04 | SDD | 04_SDD.md | Software Design Document | Architecture | /shadow-architect, /shadow-design |
| 05 | ADR | 05_ADR.md | Architecture Decision Record | Architecture | /shadow-architect |
| 06 | JUKNIS | 06_JUKNIS.md | Technical Implementation & Operations Guide | Implementation / Ops | /shadow-ops, /shadow-api |
| 07 | CONFIG | 07_CONFIG.md | Configuration Register | Implementation / Release | /shadow-ops, /shadow-sec |
| 08 | RTM | 08_RTM.md | Requirements Traceability Matrix | Verification / UAT | /shadow-test, /shadow-uat |
| 09 | TEST_PLAN | 09_TEST_PLAN.md | Software Test Plan and Execution Report | Verification / Pre-UAT | /shadow-test, /shadow-perf |
| 10 | UAT | 10_UAT.md | User Acceptance Test Plan and Report | Staging UAT | /shadow-uat |
| 11 | BUG_LOG | 11_BUG_LOG.md | Defect and Bug Register | Verification / UAT | /shadow-test, /shadow-uat |
| 12 | CHANGE_REQUEST (CR) | 12_CHANGE_REQUEST.md | Change Request and Impact Assessment | Cross-Stage Governance | /shadow-plan, /shadow-architect |
| 13 | CHANGELOG | 13_CHANGELOG.md | Change Log and Release Notes | Production Release | /shadow-release |
| 14 | INCIDENT | 14_INCIDENT.md | Production Incident Report and RCA | Post-Prod Maintenance | /shadow-maintain, /shadow-observe |
| 15 | CAPA | 15_CAPA.md | Corrective Action & Improvement Recommendations | Post-Prod Maintenance | /shadow-maintain, /shadow-resilience |
| 16 | MANUAL | 16_MANUAL.md | User, Administrator and Operator Manual | Client Handover | /shadow-handover |
| 17 | HANDOVER (BAST) | 17_HANDOVER.md | Handover Package / BAST Annex | Client Handover | /shadow-handover |
| 18 | SECURITY_RISK | 18_SECURITY_RISK.md | Security Assessment and Risk Register | Verification / Security | /shadow-sec, /shadow-auth |
| 19 | MAINTENANCE | 19_MAINTENANCE.md | Maintenance and Service Level Report | Post-Prod Maintenance | /shadow-maintain |
| 20 | DEPLOYMENT | 20_DEPLOYMENT.md | Deployment and Production Verification Record | Production Release | /shadow-release, /shadow-ops |
3. Ownership Boundaries Across Shadow Army Skills (Zero Duplication)
- Domain Skills Generate Technical Truth:
/shadow-discoveryelicits requirements & acceptance criteria -> feedsBRD_PRD&SRS./shadow-architect&/shadow-dbdesign C4, ADRs, and DB schemas -> feedSDD&ADR./shadow-test,/shadow-sec, &/shadow-perfexecute tests, security audits, and Pre-UAT load tests -> feedTEST_PLAN,BUG_LOG, &SECURITY_RISK./shadow-uatgoverns UAT scenarios & sign-off -> feedsRTM&UAT./shadow-release&/shadow-opsexecute deployments & runbooks -> feedCHANGELOG,DEPLOYMENT, &JUKNIS./shadow-handover&/shadow-maintaingovern BAST delivery, SLAs, and RCAs -> feedHANDOVER,MANUAL,INCIDENT,CAPA, &MAINTENANCE.
/shadow-docv2.0 Owns Canonical AST Governance & Multi-Format Rendering:/shadow-docowns schema validation (schemas/canonical-document.schema.json), selective block patching, cross-document traceability/impact graphs, approval state transitions, and deterministic rendering to.docx,.pdf,.xlsx,.csv,.md, and.zip.
4. CLI Reference (scripts/doc_scaffold.py)
# 1. Create a canonical v2.0 JSON document from any of the 20 templates
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" create `
--type SRS --project-id PRJ-2026 --doc-id DOC-SRS-001 `
--lang id-ID --style corporate --owner "System Analyst" --out docs/SRS.json
# 2. Import existing .md, .docx, .pdf (reference), or legacy v1 .json into v2.0 AST
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" import `
--in draft.md --project-id PRJ-2026 --type SRS --doc-id DOC-SRS-001 --out docs/SRS.json
# 3. Selectively update a single block (auto-forks new DRAFT if document is APPROVED)
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" update `
--doc docs/SRS.json --scope-id FR-001 `
--content "Sistem wajib mendukung OAuth2/OIDC dengan FIDO2 Passkey." `
--author "Security Architect" --change-ref CR-001
# 4. Validate schema, secrets, traceability, and release gates (--strict for release)
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" validate --doc docs/SRS.json --strict
# 5. Bidirectional traceability & change-impact analysis
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" impact `
--doc docs/SRS.json docs/RTM.json --changed-id FR-001
# 6. Controlled approval transition (enforces owner != actor & evidence_ref)
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" approve `
--doc docs/SRS.json --status APPROVED --actor "VP Engineering" `
--role "Approver" --evidence-ref "MINUTES-2026-11-10"
# 7. Export to DOCX, PDF, XLSX, CSV, and Markdown with automated cross-format QA
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" export `
--doc docs/SRS.json --format all --out-dir docs/output
# 8. Build stage handover ZIP bundle with SHA-256 manifest.json
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" package `
--source-dir docs/output --project-id PRJ-2026 --stage handover --out docs/Handover_Bundle.zip
# 9. Run v1.0 backward-compatibility self-test & v2.0 15-test acceptance suite
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" --selftest
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\doc_scaffold.py" --acceptance-suite
# 10. Download a reference to local PC, verify 7-Point File Safety, and update references_manifest.json
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\reference_verifier.py" fetch `
--url "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-218.pdf" `
--dest-dir docs/references --title "NIST SSDF SP 800-218" --venue "NIST" --year "2022" --doi "10.6028/NIST.SP.800-218"
# 11. Scan local reference folder and auto-delete any disguised/dangerous file
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\reference_verifier.py" scan docs/references --quarantine-delete
python "d:\Ridhuan Ngoding Moment\SKILL\shadow-doc\scripts\reference_verifier.py" --self-test- Word TOC Field Note: When opening generated
.docxfiles in Microsoft Word, pressCtrl+AthenF9to populate dynamic page numbers in the native Word Table of Contents (TOC) field. - References:
- Canonical Schema:
schemas/canonical-document.schema.json - Hybrid Schema & Migration Reference:
references/HYBRID-JSON-MD-SCHEMA.md - Full PRD/SRS Requirements:
requirements/SHADOW_DOC_V2_PRD_SRS.md
- Canonical Schema:
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

