VII (7)

janus-tier2-project

janus

Use for normal project work — repo task, bug fix, feature add, video folder, event packet, design iteration, marketing campaign, copy edit, landing page update, or resuming previous project work. The default tier when unclear.

Janus Tier 2 — Normal Project Work

IWhen To Use

  • Standard work inside a project folder, repo, video workflow, design workflow, or recurring task.
  • Some prior state matters (a folder, a repo, a previous WORKLOG).
  • Default tier when unclear.

IIWhat To Load

Required, in order:

  1. The project's .janus/PROJECT_CONTEXT.md if it exists.
  2. The project's .janus/WORKLOG.md if it exists.
  3. The relevant mode sub-skill ($janus-build-mode, $janus-content-mode, or $janus-judge-mode).

Optional, by discovery only:

  • A specific template from templates/.
  • The onslaught engineering skill ($onslaught-engineering) if the project is an Onslaught code project.

Do not load harness references (references/HARNESS_SPEC.md etc.) at Tier 2.

IIIWorkflow

  1. Read PROJECT_CONTEXT and WORKLOG if present.
  2. Pick the mode. Hand off to that mode skill.
  3. Make the smallest correct change.
  4. Verify (run tests, build, link check, lint — whatever applies).
  5. Update .janus/WORKLOG.md via $janus-worklog.

IVDiscovery Rule

Expand context only when blocked. If verification can't complete without another file, load that one file — not a whole folder.

VOutput

Completed.

Changed:
- path

Verified:
- command : result

Next:
- one action

VIEscalate When

  • Task involves a multi-step pipeline, automation, MCP, judge engine, or full system deploy → Tier 3.
  • Security review required → Tier 3, with $onslaught-engineering for Onslaught code.
← back to the stoa