agentleFS
RidhuanDEVRidhuanDEV/claude-skills/shadow-doc/SKILL.md

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.

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
  1. Very specific:

    Use this skill whenever the Monarch asks to create, import, selectively update, validate, trace, approve, render, or package formal SDLC, …

    line 8
  2. Very specific:

    All text, tables, diagrams, and metadata changes MUST be applied to the Canonical JSON AST (.json) or Markdown source (.md) and regenerated …

    line 15
  3. Very specific:

    Never invent dates, ticket IDs, metrics, stakeholder names, test results, or deployment topologies.

    line 17
  4. Very specific:

    Document owner cannot self-approve (owner != approver), and HANDOVER / BAST artifacts cannot transition to APPROVED/RELEASED without signed …

    line 21
  5. Very specific:

    All exports automatically redact leaked credentials ([REDACTED_SECRET]), reject cross-project forbidden_terms, and write files atomically …

    line 25
  6. Very specific:

    Industry Standards First: Every SDLC document (SRS, SDD, RTM, TEST_PLAN, UAT, SECURITY_RISK, INCIDENT, MANUAL, MAINTENANCE) anchors to …

    line 29
  7. Very specific:

    All 20 templates live in templates/ and are cataloged in TEMPLATE_CATALOG.md:

    line 37
  8. Very specific:

    Word TOC Field Note: When opening generated .docx files in Microsoft Word, press Ctrl+A then F9 to populate dynamic page numbers in the …

    line 130

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

  1. 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 via scripts/doc_scaffold.py.
  2. 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, or CLOSED MUST cite a verified source_refs entry. Strict validation (validate --strict) blocks release if unresolved placeholders or unverified claims exist.
  3. Approved Document Protection & Separation of Duties (DOC-FR-010, DOC-FR-011, AT-04, AT-11):
    • Documents in APPROVED or RELEASED status are immutable in-place. Calling update on an approved document automatically forks a new DRAFT revision (e.g., 1.1-DRAFT) with supersedes pointing to the approved revision.
    • Document owner cannot self-approve (owner != approver), and HANDOVER / BAST artifacts cannot transition to APPROVED/RELEASED without signed evidence_ref.
  4. 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, recording before_hash and after_hash in history[]. Concurrent edits with a stale expected_hash fail closed (CONCURRENCY_CONFLICT).
  5. Secret Scanning, Cross-Project Isolation & Atomic Rollback (AT-06, AT-10, AT-14):
    • All exports automatically redact leaked credentials ([REDACTED_SECRET]), reject cross-project forbidden_terms, and write files atomically via .tmp + .bak rollback.
  6. 100% v1.0 Backward Compatibility (AT-12):
    • Legacy v1.0 commands (--selftest, md-to-json, check-readiness) and bagian -> subbagian -> blok JSON files remain fully supported and can be migrated losslessly via migrate-v1 (preserving a .v1.bak.json backup).
  7. 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 (/context7 MCP).
    • Academic Literature & arXiv Preprint Rules: Use peer-reviewed databases (IEEE Xplore, ACM Digital Library, SpringerLink, ScienceDirect, indexed via Semantic Scholar / OpenAlex / Google Scholar) as supporting evidence when architectural or algorithmic decisions require empirical backing. Never default to arXiv for software engineering standards; arXiv preprints must be tagged source_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 into docs/references/ and verify every downloaded or imported file with scripts/reference_verifier.py (checks extension allowlist, double-extension spoofing, %PDF- vs MZ/ELF magic bytes, PDF /JavaScript & /Launch exploit tokens, HTML <script> injection, and SHA-256 manifest; unsafe files are immediately deleted from the local PC).

2. Catalog of 20 Standardized SDLC Templates (templates/01..20)

All 20 templates live in templates/ and are cataloged in TEMPLATE_CATALOG.md:

#Type CodeTemplate FileDocument TitlePrimary SDLC StageCollaborating Skill
01SDLC_PLAN01_SDLC_PLAN.mdSoftware Development Lifecycle PlanDiscovery / Planning/shadow-plan
02BRD_PRD (PRD, BRD)02_BRD_PRD.mdBusiness and Product RequirementsDiscovery/shadow-discovery
03SRS03_SRS.mdSoftware Requirements SpecificationDiscovery/shadow-discovery
04SDD04_SDD.mdSoftware Design DocumentArchitecture/shadow-architect, /shadow-design
05ADR05_ADR.mdArchitecture Decision RecordArchitecture/shadow-architect
06JUKNIS06_JUKNIS.mdTechnical Implementation & Operations GuideImplementation / Ops/shadow-ops, /shadow-api
07CONFIG07_CONFIG.mdConfiguration RegisterImplementation / Release/shadow-ops, /shadow-sec
08RTM08_RTM.mdRequirements Traceability MatrixVerification / UAT/shadow-test, /shadow-uat
09TEST_PLAN09_TEST_PLAN.mdSoftware Test Plan and Execution ReportVerification / Pre-UAT/shadow-test, /shadow-perf
10UAT10_UAT.mdUser Acceptance Test Plan and ReportStaging UAT/shadow-uat
11BUG_LOG11_BUG_LOG.mdDefect and Bug RegisterVerification / UAT/shadow-test, /shadow-uat
12CHANGE_REQUEST (CR)12_CHANGE_REQUEST.mdChange Request and Impact AssessmentCross-Stage Governance/shadow-plan, /shadow-architect
13CHANGELOG13_CHANGELOG.mdChange Log and Release NotesProduction Release/shadow-release
14INCIDENT14_INCIDENT.mdProduction Incident Report and RCAPost-Prod Maintenance/shadow-maintain, /shadow-observe
15CAPA15_CAPA.mdCorrective Action & Improvement RecommendationsPost-Prod Maintenance/shadow-maintain, /shadow-resilience
16MANUAL16_MANUAL.mdUser, Administrator and Operator ManualClient Handover/shadow-handover
17HANDOVER (BAST)17_HANDOVER.mdHandover Package / BAST AnnexClient Handover/shadow-handover
18SECURITY_RISK18_SECURITY_RISK.mdSecurity Assessment and Risk RegisterVerification / Security/shadow-sec, /shadow-auth
19MAINTENANCE19_MAINTENANCE.mdMaintenance and Service Level ReportPost-Prod Maintenance/shadow-maintain
20DEPLOYMENT20_DEPLOYMENT.mdDeployment and Production Verification RecordProduction Release/shadow-release, /shadow-ops

3. Ownership Boundaries Across Shadow Army Skills (Zero Duplication)

  • Domain Skills Generate Technical Truth:
    • /shadow-discovery elicits requirements & acceptance criteria -> feeds BRD_PRD & SRS.
    • /shadow-architect & /shadow-db design C4, ADRs, and DB schemas -> feed SDD & ADR.
    • /shadow-test, /shadow-sec, & /shadow-perf execute tests, security audits, and Pre-UAT load tests -> feed TEST_PLAN, BUG_LOG, & SECURITY_RISK.
    • /shadow-uat governs UAT scenarios & sign-off -> feeds RTM & UAT.
    • /shadow-release & /shadow-ops execute deployments & runbooks -> feed CHANGELOG, DEPLOYMENT, & JUKNIS.
    • /shadow-handover & /shadow-maintain govern BAST delivery, SLAs, and RCAs -> feed HANDOVER, MANUAL, INCIDENT, CAPA, & MAINTENANCE.
  • /shadow-doc v2.0 Owns Canonical AST Governance & Multi-Format Rendering:
    • /shadow-doc owns 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 .docx files in Microsoft Word, press Ctrl+A then F9 to 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.