Harnass Engineer Start

Read documents/router.yaml.

This skill owns the canonical scaffold source under documents/shared/.

Use scripts/bootstrap_target_repo.py . --mode auto --overwrite-policy create-or-merge to materialize the target repo scaffold (. = current working directory, which is the target repo root), then scaffold the frontend-design route without doing design generation.

Do:

• create target repo harnass-os/
• own the canonical scaffold source inside this skill's documents/shared/
• materialize target repo templates from the canonical spec
• run scripts/bootstrap_target_repo.py . --mode auto --overwrite-policy create-or-merge
• emit root entry files: AGENTS.md, CLAUDE.md, Plan.md, Architecture.md
• emit canonical runbooks under harnass-os/: Implement.md, Deploy.md, Audit.md, Documentation.md
• emit canonical intake, design, runtime, release, audit, run, status, decision, design validation, deploy, route, and handoff skeletons under harnass-os/documents/
• emit browser-audit report scaffolding under harnass-os/documents/audit/browser/
• write the mandatory route for the external frontend-design skill on ui-facing work
• wire the post-production final audit route and release-signoff gates
• wire hooks, guard entry, validation, and worktrees

Do not:

• do research, ask-user, or planning
• do not generate final ui pages
• skip bootstrap gates

Gates:

• documents first
• templates before placeholders
• bootstrap engine before scaffold-complete
• frontend-design route before ui execution
• full scaffold before planning
• planning belongs to harnass-engineer-plan