Update to Codex Dev Workflows

{
  "description": "Turn a new software idea into a scoped, buildable project plan before implementation begins.",
  "included_files": [],
  "name": "new-project",
  "skill_md_contents": "---\nname: new-project\ndescription: Turn a new software idea into a scoped, buildable project plan before implementation begins.\n---\n\n# New project workflow\n\nUse this skill when the user is starting a project, validating an idea, or asking for a practical implementation plan. Ask only for information that materially changes the plan; otherwise state reasonable assumptions.\n\n## Discover\n\n1. Restate the product goal, target users, and the smallest useful first release.\n2. Identify constraints: target platforms, preferred stack, integrations, privacy/security needs, accessibility, timeline, budget, deployment, and data ownership.\n3. Separate confirmed requirements from assumptions and open decisions.\n4. Define non-goals for the first release so the plan stays tractable.\n\n## Design before building\n\nPropose a lightweight foundation appropriate to the project:\n\n- a short product brief and acceptance criteria;\n- an architecture outline with major components and data flows;\n- repository documentation for architecture, testing, design/system rules, and domain-specific rules when relevant;\n- concise agent instructions that route an agent to authoritative project documentation;\n- an ordered backlog of small, independently verifiable milestones.\n\nChoose technology only when the user has supplied a preference or trade-offs can be explained concisely. Do not pretend a decision is final when it remains open.\n\n## Build plan\n\nFor each milestone, state the user-visible outcome, implementation boundary, dependencies, tests/validation, and completion criteria. Put risky assumptions, security-sensitive work, and irreversible data decisions early enough to validate before substantial build effort.\n\n## Final response\n\nReturn:\n\n- project summary and first-release scope;\n- requirements, assumptions, and non-goals;\n- recommended repository/documentation structure;\n- architecture and data-flow outline;\n- milestone plan with acceptance criteria;\n- immediate next action and unresolved decisions.\n\nDo not start implementation unless the user asks for it.\n\n"
}