From envicon-workflow
Guide PE review of drafted Phase 1 sections in Obsidian and export to docx via Pandoc. Use when reviewing report drafts, filling placeholders, or preparing final export.
How this skill is triggered — by the user, by Claude, or both
Slash command
/envicon-workflow:obsidian-report-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. Launch Obsidian → **Open folder as vault**
LegalVault/, Projects/)Projects/<project-name>/00_Project_Dashboard.mdThe dashboard transcludes all 8 section files. Edits in embedded sections update the source files.
For each section in Report_Sections/:
> **DRAFT — PE REVIEW REQUIRED**<!-- FILL IN MANUALLY: ... --> blocks completed<!-- DRAFT: ... --> AI narratives reviewed and correctedLegalVault/ filesEDR_Database_Hits/ have classification (REC/CREC/HREC/De Minimis)| Location | Purpose |
|---|---|
EDR_Database_Hits/ | Per-site database records from EDR |
Historical_Records/ | Historical source observations |
Site_Notes/ | PE scratch notes |
_writer_notes.md | Writer agent session notes |
Use Obsidian wikilinks [[note-name]] to cross-reference hits and sections.
After PE review is complete, run export (paths assume Phase 1 Report Generator layout):
python pipeline.py --project Projects/<project-name> --phase export
Output:
Projects/<project-name>/Export/<project-name>_Phase1_ESA_DRAFT.docx
Optional PDF:
python pipeline.py --project Projects/<project-name> --phase export --pdf
Note: Pandoc does not resolve Obsidian ![[]] transclusion. Export concatenates section markdown files directly — ensure section files are complete before export.
TemplateVault/pandoc/reference.docx present for styled outputnpx claudepluginhub shivansh-dutta/envicon-workflow-plugin --plugin envicon-workflowCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.