agentleFS
Sign inStart free
phoenixvnphoenixvn/claude-code-agency/.claude/skills/intake/SKILL.md

intake

Skill0 starsChanged 7 months agoMITView on GitHub

Gather all project requirements through a structured conversation and produce a comprehensive client brief. Question 1: "What type of project is this?" Options: Website / Web Application / Mobile App / Branding / Marketing Campaign / Content Strategy / SEO / Full-service (multiple) Question 2: "Tell me about the business." Ask for: Company name, industry, current digital presence, what makes them unique. Question 3: "What are the primary goals?" Options: Increase sales / Generate leads / Build brand awareness /…

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan, triage and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 4 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 4 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 33 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Use AskUserQuestion to gather high-level info:

    line 8
  2. Distinctive:

    Ask for: Company name, industry, current digital presence, what makes them unique.

    line 14
  3. Distinctive:

    Ask for: Demographics, needs, pain points, how they currently find the business.

    line 20
  4. Distinctive:

    Ask about known competitors (2-3 minimum)

    line 31
  5. Very specific:

    Read the template from .claude/docs/templates/client-brief.md.

    line 44
  6. Very specific:

    Ask for approval. On approval, update production/session-state/active.md with:

    line 56

“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “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

/intake — Client Brief Intake

Gather all project requirements through a structured conversation and produce a comprehensive client brief.

Instructions

Phase 1: Initial Briefing

Use AskUserQuestion to gather high-level info:

Question 1: "What type of project is this?" Options: Website / Web Application / Mobile App / Branding / Marketing Campaign / Content Strategy / SEO / Full-service (multiple)

Question 2: "Tell me about the business." Ask for: Company name, industry, current digital presence, what makes them unique.

Question 3: "What are the primary goals?" Options: Increase sales / Generate leads / Build brand awareness / Improve user experience / Launch new product / Enter new market

Question 4: "Who is the target audience?" Ask for: Demographics, needs, pain points, how they currently find the business.

Phase 2: Requirements Deep-Dive

Spawn the business-analyst agent to:

  • Dig into functional requirements (features, capabilities, integrations)
  • Identify non-functional requirements (performance, security, accessibility, browser support)
  • Map user stories or use cases
  • Define acceptance criteria for key requirements

Phase 3: Competitive Context

Spawn the market-researcher agent to:

  • Ask about known competitors (2-3 minimum)
  • Identify market positioning opportunities
  • Note key differentiators

Phase 4: Scope & Constraints

Use AskUserQuestion for:

  • Budget range (if the client wants to share)
  • Hard deadlines or key dates
  • Technical constraints (existing tech stack, hosting, CMS preferences)
  • Existing brand assets (logo, colors, fonts, brand guidelines)
  • Any reference sites they admire and why

Phase 5: Brief Compilation

Read the template from .claude/docs/templates/client-brief.md. Compile all gathered information into a comprehensive brief. Save to briefs/[client-name]-brief.md (kebab-case client name).

Phase 6: Review & Approval

Present a summary of the brief to the user:

  • Project type and scope
  • Key goals and KPIs
  • Target audience summary
  • Top requirements
  • Constraints and timeline

Ask for approval. On approval, update production/session-state/active.md with:

## Current Client: [Client Name]
## Current Phase: Discovery

Suggest next step: /discover for research, /proposal for proposal, or /kickoff to jump straight in.

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.

Check your setup, free