agentleFS
attilaszaszattilaszasz/sdd-pilot/.agents/skills/sddp-prd/SKILL.md

sddp-prd

Skill98 starsChanged 28 days agoMITView on GitHub

Create or refine the canonical product document. Direct command-bar dispatch only; do not select for general queries.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create or refine the canonical project Product Requirements Document only.

    line 9
  2. Very specific:

    If the user provided no message, set $ARGUMENTS to empty and let the shared workflow handle it.

    line 13
  3. Distinctive:

    When the shared workflow asks the user to choose, confirm, or answer:

    line 19
  4. Distinctive:

    Ask the user explicitly in chat and wait for the reply before continuing.

    line 20
  5. Distinctive:

    Do not infer an answer from silence, a partial response, or prior recommendations.

    line 23
  6. Very specific:

    Do not browse ad hoc. Only when the workflow says Delegate: Technical Researcher, read .github/agents/_technical-researcher.md at that …

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Argument hint: [rough product idea, users, domain, or market opportunity] Command category: project-bootstrap Prerequisites: none

Create or refine the canonical project Product Requirements Document only. Ignore feature-level implementation context.

Input

$ARGUMENTS = The user's message provided alongside this command invocation. If the user provided no message, set $ARGUMENTS to empty and let the shared workflow handle it.

Pass $ARGUMENTS through to the shared workflow. No mode flag defaults to --quick. Supported controls are --quick, --discover, --resume, and --skip-research; the shared workflow owns their behavior.

Load and follow the workflow in .github/sddp/workflows/product-document/WORKFLOW.md.

When the shared workflow asks the user to choose, confirm, or answer:

  • Ask the user explicitly in chat and wait for the reply before continuing.
  • Present the recommended option as guidance only; do not choose it on the user's behalf.
  • Allow free-form answers anywhere the shared workflow allows them.
  • Do not infer an answer from silence, a partial response, or prior recommendations.

Do not browse ad hoc. Only when the workflow says Delegate: Technical Researcher, read .github/agents/_technical-researcher.md at that point and perform only that delegated step.

Report milestone progress.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.