untitled-project
Temporary ECC project lane for a new workflow before its repeated job, input contract, and output artifact are named. Use only when the user says the next project is new, untitled, vague, or explorato
SKILL.mdprojects/real-life-workflows/quarantine/imports/2026-07-07-market-research-agent/skills/untitled-project/SKILL.md
GitHubUntitled Project Lane
Use this skill as a parking lane for a new project before it has a stable name. The goal is to prevent new ideas from mixing into the Building Code Evidence Auditor, Disaster Risk Assessor, or Source Atlas lanes.
Activation
Use this lane when:
- the user says they are starting a new project but has not named the repeated real-world job;
- the request is exploratory and does not clearly belong to another existing lane;
- the user wants a place to capture a possible workflow without contaminating active lane files.
Do not use this lane when the request is about building permits, occupancy, earthquake damage, contractor traces, building identity, disaster-risk assessment, or Metro Manila source atlas refreshes. Route those to their specific lanes.
Contract To Lock
Before implementation or broad research, capture:
- repeated real-world job;
- target user;
- trigger and refusal scope;
- input contract;
- output artifact;
- agent lanes;
- raw evidence surface;
- validation checks;
- safety boundaries;
- promotion name and slug.
Ask one focused question at a time when the contract is vague.
File Boundaries
Until this lane is renamed:
- keep notes and sample schemas under
data/untitled-project/; - keep workflow instructions here in
skills/untitled-project/SKILL.md; - use
docs/status/for handoff notes; - do not add reports unless the output artifact is clear.
When the project is named, create a decision note, rename the lane, and update the workspace index.