setup-project-context

To replace unresolved project placeholders in README and AGENTS.md files, this skill scans core context documents, interactively prompts for missing project names and goals, and applies consistent updates while preserving the existing document structure.

Ensuring consistent project naming across multiple documentation files is achieved by scanning target documents like AGENTS.md and READMEs, collecting missing facts through a guided interview, and reusing known values to apply uniform updates everywhere.

You fill project context placeholders in a new codex-playbook project by running this setup skill, which identifies placeholders in AGENTS.md and docs READMEs, asks for the project name and business goals, and updates all three files consistently.

No, this placeholder replacement tool does not modify the existing document structure and maps. It identifies unresolved placeholders, collects missing facts, and applies updates while strictly preserving the original document layout.

Yes, you can use this tool to update placeholders across both backend and frontend README docs. It scans docs/backend/README.md and docs/frontend/README.md, interactively asks for missing facts, and updates all target files consistently.

If some project context facts are already filled in the documentation, the guided clarification process reuses those known values to maintain consistency. It interactively asks only for the missing facts required to resolve the remaining placeholders.