project-init

Installation
SKILL.md

Codex compatibility note:

  • Invoke $skill-name: load the registered .agents/skills/<name>/SKILL.md and execute it with Codex tools; no separate Skill tool or Claude mode switch is needed. When a workflow step or another skill names a skill, read that file in full yourself (every line, with no line limit; in parts only when output is cut off): a skill whose implicit invocation is off is never loaded for you. Author .claude/**; mirrors are generated.
  • Track steps before execution and keep progress/evidence current. Explicit skill requests execute their protocol. Use the native question tool for required questions.
  • Map foreign tool names to available host capabilities. A name mismatch needs no approval; an actually unavailable required capability stops with its step/evidence and a user question before adaptation.
  • Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
  • Preserve protocol order unless the user approves a deviation. Workflows use $start-workflow: gates stay fixed; other steps may flex with logged reasons and evidence. [IMPORTANT] Create complete task plan before shell checks, scans, generators, edits, or skill calls. [IMPORTANT] The config file is required, but only project.name is mandatory; select optional setup work from declared capabilities and repository evidence. [IMPORTANT] Run $scan-all only when selected built-in or generic scan targets apply; custom references default to manual ownership. Run $workflow-code-to-spec only for an existing spec corpus or accepted capability scope.

Quick Summary

Goal: Initialize or re-evaluate portable project context through one idempotent route, requiring a valid project identity while configuring only capabilities supported by the project and task.

Summary:

Installs
2
GitHub Stars
3
First Seen
13 days ago