heymegabyte/agent-skills / 02-goal-and-brief
goal-and-brief
VerifiedEstablish project thesis before first code. Infer product type from domain/folder/README. Identify users, business model, pSEO strategy, AI-native dev approach. Maintain PROJECT_BRIEF.md as source of truth.
02 — Goal and Brief
Establish the project thesis and maintain PROJECT_BRIEF.md as the source of truth before any code is written.
Run FIRST on every new project / rebuild
Before code, write PROJECT_BRIEF.md. The brief drives every downstream decision (skill 05 stack, skill 06 build, skill 09 brand, skill 16 site mode).
One-line website prompt? Hand off after the brief:
16-cinematic-website-prime-directiveis the prime directive (trumps generic 06-build);website-build-manifestis the acceptance index of every gate;website-build-doctrineis the Phase -1→8 sequence. Brief → manifest → doctrine → build.
Org-type inference (drives everything)
Detect from domain + folder name + scraped homepage + Google Places category:
| Pattern | Org type |
|---|---|
*.com w/ pricing page + signup → | saas |
*.org w/ donate button + 501(c)(3) → | nonprofit |
| Google Places category in {restaurant, salon, medical, legal, fitness, automotive, retail, photography, real-estate, education, financial, pet, wedding} → | local-business |
*.com portfolio of links + bio + projects → | portfolio |
*.gov / .gov.uk / .ca.gov → | government |
*.edu / *.ac.uk → | edu |
*.church / parish JSON-LD → | church |
| ProductHunt / G2 / Capterra listing → | saas |
Output: _org_type.json = {type, confidence, evidence[]}.
PROJECT_BRIEF.md (source of truth)
# {Project Name}
## Thesis
One sentence: what this project does + for whom + why now.
## Org type
{saas | nonprofit | local-business | portfolio | edu | gov | church}
## Primary user
- Persona: {role + context}
- Job to be done: {task they're trying to accomplish}
- Success metric: {what "done" looks like for them}
## Business model
- Revenue: {subscription / donation / one-time / B2B / B2C / ads}
- Pricing: {tier list w/ values}
- Margins: {high / medium / low + rationale}
## pSEO strategy (5 types)
- Integration pages (`/integrations/{tool}`) — Y/N
- Comparison (`/compare/{a}-vs-{b}`) — Y/N
- Use-case (`/for/{audience}`) — Y/N
- Template (`/templates/{type}`) — Y/N
- Location (`/{city}-{service}`) — Y/N
## AI-native development approach
- AI-first features: {list}
- Workers AI / Llama 4 Scout for first-pass content
- Opus 4.8 for top-10 conversion polish
- AI vision QA on every visual surface
## Constraints
- Budget
- Timeline
- Compliance (HIPAA / SOC 2 / GDPR / FERPA / ADA)
- Localization needs (`_kernel/standards.md` § ADA + `rules/i18n-by-demographics.md`)
## Decision log
{Every architectural decision + rationale + alternatives considered}
Question discipline
- Before code, scan brief for gaps. Use
AskUserQuestionONLY for genuinely unresolvable items (e.g., bilingual-staff confirmation, NAP verification, license number). - Per
brian-preferences.md: pick ONE answer when inferable, never offer options. - Silence = approval.
What this skill produces
PROJECT_BRIEF.md— committed_org_type.json— input to skill 05 (stack) + skill 09 (brand) + skill 16 (site mode)_brief_summary.txt— 100-word digest for downstream agents
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |