SkillsAdd

smithery/rafaie

project-intake

Bootstrap a target repository with stack-aware SDLC templates, smoke starters, and a concise project brief. Use when starting a new project or adopting this workflow in an existing repo.

Installation

$ npx skills add smithery/rafaie --skill project-intake
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from smithery/rafaie.

npx skills add smithery/rafaie
test-plan 0

Browse all from smithery/rafaie

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents codex

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,072 B
  • docs SUMMARY.md 106 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

  1. Confirm you are in the target project repo, not the global Codex home directory.

- If the current repo is /Users/mostafa/.codex or another Codex home, stop and ask for the target project path. - If the repo already has AGENTS.md, follow it first.

  1. Resolve templates from the active Codex home templates/ directory, then bootstrap missing SDLC files.

- Create missing directories: spec/, spec/templates/, spec/decisions/, spec/features/, scripts/. - Create AGENTS.md from templates/AGENTS.md only if missing. - Create codex.toml from templates/codex.toml only if missing. - Copy starter templates into spec/templates/ only if missing: - adr.md - architecture.md - backlog.md - feature.md - implementation.md - test-plan.md - test-results.md - status.md - evidence.md - docstrings.md - specindex.md - Create smoke starters only if missing: - spec/smoke.md from templates/smoke.md - spec/smokeregistry.yaml from templates/smoke_registry.yaml - scripts/smoke.py from templates/smoke.py - Keep placeholder scenarios disabled until a real entrypoint, fixture, schema/invariants, and mode behavior are configured. - Create spec/docstrings.md from templates/docstrings.md only if missing. - Do not overwrite existing repo-local files unless the user explicitly asks.

  1. Read the user’s project idea (or spec/idea.md if it exists), plus the newly bootstrapped AGENTS.md and codex.toml.

- Detect the project stack and replace Python/uv command placeholders only when the correct commands can be inferred safely; otherwise list every required customization. - Apply the Google-style docstring policy only to Python code.

  1. Ask up to 5 targeted questions only if essential info is missing (goal, users, constraints, success metrics).
  2. Create/update:

- spec/brief.md (1–2 pages) with: Goal, Users, Scope/Non-scope, Constraints, Risks, Milestones. - spec/index.md (navigation hub) with links to brief, architecture, ADRs, and backlog. - Prefer spec/templates/spec_index.md for a new spec/index.md.

  1. Initialize the project workflow state:

- Ensure spec/changelog.md exists with an initial entry. - Ensure spec/decisions/ exists; do not create an ADR unless a real decision is present. - Leave spec/backlog.md for backlog-builder unless the user explicitly asks to create it now.

  1. End with:

- Files created - Files preserved because they already existed - Any commands the user should customize in codex.toml - Smoke scenario/fixture/schema/mode fields that must be customized before enabling smoke - Proposed “first 3 work items” list (thin vertical slices) - Exact next command: Run $backlog-builder