Guide discovery conversations and generate PRD, TECH-SPEC, PROGRESS, and CONTEXT documentation.
npx skills add https://github.com/tygwan/ultra-codex-init --skill init-tygwan
Please help me install this Agent Skill. Skill: init Source: https://github.com/tygwan/ultra-codex-init/tree/main/.codex/skills/init Command: npx skills add https://github.com/tygwan/ultra-codex-init --skill init-tygwan
Kickstart new code projects by guiding discovery conversations and generating foundational documentation to reduce ambiguity and accelerate alignment.
Run /init --full to start a discovery-driven project setup and generate initial documentation.
High-intent search queries and answers about installing and using this skill.
To generate project documentation like a PRD and tech spec from scratch, run a guided discovery conversation that uncovers goals and constraints, then automatically scaffolds PRD, TECH-SPEC, PROGRESS, and CONTEXT files.
Kickstarting a new code project with discovery-led setup reduces early ambiguity by guiding conversations with stakeholders to capture requirements, then scaffolding foundational documentation for immediate team alignment.
Yes, you can initialize documentation for an existing evolving codebase by using an optional synchronization workflow that merges generated discovery components and structured templates into your current repository.
Guided discovery works by prompting you with targeted questions to uncover project goals, constraints, and stakeholders, then translating those answers into structured documentation files within a .codex framework.
No dependencies are required to scaffold project context and templates; the setup framework independently generates the .codex structure and ready-to-use documentation templates directly within your environment.
You should avoid an automated discovery process for project setup when your team already maintains rigid, established documentation workflows, as merging generated PRD and tech spec templates may conflict with existing conventions.
claudeforgePlan software projects by guiding discovery, requirements gathering, and scoping into a structured plan.
lync-cyberAnalyze change requests against PRD, ARCH, UI-SPEC, and DEV-PLAN documents.
owebboyAutomate end-of-session code review, documentation updates, and task tracking.
leanpubGuide authors through collaborative onboarding to generate a book outline.
