Claude Code ndf-project-brief-runner skill for scoping a project
Write an advisory project brief with its goal, scope, non-goals, architecture hints, risks, and next steps.
中文Install in Claude Code
A local Claude Code project using NDF rules and matching skills from the same pinned GitHub revision. The maintainer reviews the advisory output.
- Review `.claude/skills/ndf-project-brief-runner/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/ndf-project-brief-runner/` in your project and save the reviewed file as `.claude/skills/ndf-project-brief-runner/SKILL.md`.
- Start Claude Code from that project's root, then select `/ndf-project-brief-runner` in the slash menu.
Example task
Invoke /ndf-project-brief-runner and draft a public-neutral brief from this fictional route map case.
project goal `publish a local route map` | scope `import a table of stops`
non-goal `live device tracking` | architecture hint `static Markdown index`
risk `stop names change seasonally` | next step `confirm example data with maintainer`What to check
Use `publish a local route map` as the goal. Keep `import a table of stops`, `static Markdown index`, and the `live device tracking` non-goal. Set `confirm example data with maintainer` as the next step.
Original SKILL.md on GitHub · Updated
Frequently asked question
Should a public brief include internal project names?
Use shareable context for a public brief. Keep internal details in the appropriate project documentation.