project-init
Project Init
Run this workflow only for greenfield initialization.
1. Mode Guard
Before interviewing, check:
- If both
docs/architecture.mdanddocs/plans.mdexist, stop and switch toproject-update. - If docs are missing but code roots/manifests exist (
src/,app/,apps/*/src,package.json, etc.), stop and switch toproject-convert. - Continue only when docs are missing and codebase signals are absent.
2. Interactive Interview
Collect requirements before generating any docs:
- Ask project name and core goals.
- Run one market snapshot (similar products, patterns to reuse/avoid).
- Draft project intro + end-to-end core flow and confirm with the user.
More from phlegonlabs/skills
project-long-task
>
14harness-engineer-cli
>
10full-project-skill
>
4project-update
>
3project-convert
>
3harnass-engineer-plan
Research an existing repository, align with the user, and generate a reviewed machine-readable execution plan. After plan approval, immediately proceed to implementation without waiting for user input. Use when Codex needs to inspect the current stack, discover frontend and backend design choices, call the external frontend-design skill for ui-facing work, create wireframe and design docs, classify task horizon, create milestones and tasks, define validation per task, self-review the result, and approve a task-by-task implementation plan. When the target repo lacks the `harnass-os/...` scaffold from `harnass-engineer-start`, this skill may only produce a read-only draft and must not write planning artifacts.
1