Menu
Use when initializing baseline coverage for one bounded research scope unit by staging source, artifact, finding, and claim records into a candidate bundle.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when producing a cross-record synthesis report for one domain or bounded set of taxonomy scope units after baseline review or review update records have been published.
Use when deciding whether an appraised candidate bundle should receive comments, changes requested, rejection, approval, or publication.
Use when verifying one appraisal lane for one candidate bundle revision before editorial approval or publication.
Use when checking an already scoped research unit for material changes since the latest baseline-review pass, publication, or review-update pass.
Use when drafting or revising paper-facing literature-review prose from already-collected research records, especially background sections that need inline source citations for substantive claims.
Use when deciding what needs attention now in the active lit-review-studio domain, including coverage gaps, bundle readiness, source-access issues, source-summary gaps, and thin claim support.
| name | baseline-review |
| description | Use when initializing baseline coverage for one bounded research scope unit by staging source, artifact, finding, and claim records into a candidate bundle. |
Create a candidate bundle for exactly one taxonomy scope unit. Keep public claims traceable to staged findings and sources.
lit-review-studio.config.json and the active LIT_REVIEW_STUDIO_DOMAIN value.domain-packs/<domain-id>/domain.jsondomain-packs/<domain-id>/taxonomy.v1.jsondomain-packs/<domain-id>/evidence-ladder.v1.jsondomain-packs/<domain-id>/extraction-schema.v1.jsondomain-packs/<domain-id>/appraisal-lanes.v1.jsondomain-packs/<domain-id>/skills/baseline-review.mdresearch/state/coverage-status.v1.jsonresearch/backlog/priority-queue.v1.jsondata/sources, data/artifacts, data/findings, data/claims, and data/candidate-bundles.data/staged-records/<bundle-id>/. A baseline bundle normally includes one source, one artifact when applicable, one finding, and one claim.data/candidate-bundles/<bundle-id>.json with intake_mode: "baseline_review", scoped taxonomy IDs, proposed changes, staged paths, required appraisal lanes, and source IDs/URLs.research/sessions/ that records the scope, source screening, staged output, and next actions.npm run validate
LIT_REVIEW_STUDIO_DOMAIN=<domain-id> npm run research:bundle -- validate --bundle <bundle-id>
npm run sync:research-planning
data/staged-records/<bundle-id>/.data/candidate-bundles/.research/sessions/.npm run validate and bundle validation for the active domain.