agentleFS
vivekschaudharyvivekschaudhary/compass/.claude/skills/create-product-brief/SKILL.md

create-product-brief

Skill2 starsChanged 22 days agoMITView on GitHub

Create the engagement's product brief (PM + Researcher) as a page in the docs system, gated by two Jira approval tickets. Head of the lifecycle — run before the MVP plan and any epic.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read that workflow file now and follow it step by step.

    line 8

≈ “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

Execute the workflow at compass/archive/workflows/create-product-brief.md.

Read that workflow file now and follow it step by step. Load the agent file named by each step (compass/agents/researcher.md, compass/agents/pm.md, compass/agents/delivery-manager.md) when entering it.

This workflow is docs-primary. The research page and the product brief live in the engagement's docs system (connectors.docs), under a per-engagement parent page. Nothing is written to the project repo — no file, no stub, no cache. If the docs system or Jira cannot be reached, REFUSE; never fall back to a local file.

Two human gates, two tickets. Step 2 gates on the research-review ticket; step 4 gates on the product-brief-approval ticket. Approval means the ticket reaches Jira's done status category. Never self-approve.

Elicit, don't infer. On any material unknown — always including auth posture, data sensitivity, and regulatory regime — stop and ask with 3 concrete options plus "Other (specify)", and record the answer verbatim.

Log decisions, risks, and issues to artifact DRI sections per compass/templates/dri-log-section.md.

$ARGUMENTS

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.