lucasilverentand/project-brief
plugins/project-docs/skills/project-brief/SKILL.md
Writes project brief documents from the project-docs template. Use when the user asks for a project brief, wants a one-page kickoff or framing document, needs scope and success criteria for a new project, or is filling project-brief.md.
$ install --global
skillsauthnpx skillsauth add lucasilverentand/skills project-briefInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 7:16 AM125.5s2 files scanned
SKILL.md
- name:
- project-brief
- description:
- Writes project brief documents from the project-docs template. Use when the user asks for a project brief, wants a one-page kickoff or framing document, needs scope and success criteria for a new project, or is filling project-brief.md.
Project Brief
Use this skill to turn early project intent into the project-level anchor: why it should exist, what is in scope, and how success will be judged.
Decision tree
- What is the user asking for?
- A new project brief -> read
../../README.mdandreferences/template.md, then draft the brief in the requested destination. - Audience detail or market assumptions -> use the
customer-profileskill and link to that document from the brief instead of copying the detail. - Feature behavior or acceptance criteria -> use the
feature-specskill and keep only project-level scope in the brief. - External platform, vendor, API, OS, or hardware dependency -> use the
platform-dependencyskill and link to it from the brief. - Something else -> ask one short question about whether the user needs project framing or a narrower downstream document.
- A new project brief -> read
Workflow
- Read
../../README.mdfor shared conventions and the project-docs chain. - Read
references/template.mdbefore drafting or editing. - Gather the project name, audience, reason to exist, core experience, scope boundary, success criteria, risks, and open questions.
- Keep it compact. The brief should be enough to justify the project and point to deeper docs.
- Use
related:for customer profile, platform dependency, and feature spec links when those documents exist or are planned. - Remove prompt comments from sections you fill. Leave open questions explicit instead of hiding uncertainty in polished prose.
Document contract
- When to write: At the start of a project, before commitment.
- How many: One per project.
- Owns: Project purpose, principles, scope boundary, success criteria, assumptions, and open questions.
- Link instead of duplicating: Audience detail, feature behavior, dependency analysis, technical implementation, and release evidence belong in their own documents.
Related Skills
lucasilverentand/foundations
development
VerifiedTrustedCommunity
Cross-platform Apple Human Interface Guidelines: color, typography, layout, materials, motion, accessibility, SF Symbols, branding, plus shared UI elements (activity views, rating indicators, web views, …) and meta sections (components, patterns, technologies). Use when the design topic is platform-agnostic. User says: "iOS color tokens", "SF Symbols", "Apple typography", "dark mode guidance".
3SKILL.mdUpdated Jun 13, 2026
lucasilverentand/design-workflow
development
VerifiedTrustedCommunity
Guides a full system design from idea to spec — sequences requirements gathering, architecture decomposition, data modeling, API design, and document writing into a coherent workflow with clear handoffs. Use when the user asks to "design a system", "build X from scratch", "architect something end-to-end", "plan a new service", or has a broad design ask that spans multiple concerns. Also use when the user says things like "I need to build X" without specifying which aspect to start with. This is the entry point for any design task that isn't clearly scoped to a single skill (data model only, API only, etc.).
3SKILL.mdUpdated Jun 13, 2026
lucasilverentand/design-system
development
VerifiedTrustedCommunity
Synthesizes build-ready design systems and DESIGN.md files from chat briefs, screenshots, moodboards, videos, URLs, live pages, or local image folders while preserving the target product identity. Use when the user asks to "make a design system from these screenshots", "turn this moodboard into DESIGN.md", "extract the design language from this video", "define the UX vibe and rules from these references", or create cohesive UI rules from visual inspiration.
3SKILL.mdUpdated Jun 13, 2026
lucasilverentand/design-review
development
VerifiedTrustedCommunity
Reviews and critiques an existing or proposed system design — flags single points of failure, missing non-functional requirements, scaling bottlenecks, security gaps, operational blind spots, unjustified tech choices, and places where the design will fall over under load or failure. Produces a structured review with severity-tagged findings, not just vibes. Use when the user asks for a second opinion on an architecture, requests a design review, wants feedback on a proposed system, pastes a design doc, or says things like "review this design", "what's wrong with X", "poke holes in this", or "is this a good architecture".
3SKILL.mdUpdated Jun 13, 2026