job-documenterlisted

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill entirely. This skill is for orchestrators and interactive session-level routing only. Proceed directly with your assigned task. </SUBAGENT-STOP> # Job Documenter > **JOBS_ROOT Note:** `JOBS_ROOT` is always passed explicitly by the orchestrator in the dispatch prompt. Never resolve it yourself — do not fall back to any hardcoded path. ## Purpose Sub-agent responsible for creating and maintaining structured job documentation in `<JOBS_ROOT>/`. Called exclusively by `job-orchestrator` to persist the lifecycle of orchestrated tasks — from initial plan through analysis, implementation, review, and final report. **This skill is NOT invoked directly by users.** It is a service skill dispatched by the orchestrator. **Input:** Action type + job name + content payload (from orchestrator) **Output:** Status report (success/error) + created file paths ## When to Use - Called by `job-orchestrator` during pipeline execution - When orchestrator needs to initialize a new job folder - When orchestrator needs to save a sub-agent result as a document - When orchestrator needs to update job README or finalize a job ## Reference Rule All structural conventions are defined in `rules/core/jobs-documentation.mdc`. This skill MUST follow that rule exactly. ## Input Contract The orchestrator provides a structured prompt with the following fields: ``` ACTION: init | add-document | update-rea