project-brief

Transform unstructured project ideas into structured briefs with goals and milestones.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/omerreish-lgtm/secretary-system --skill project-brief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-brief
Source: https://github.com/omerreish-lgtm/secretary-system/tree/main/skills-source-project-brief
Command: npx skills add https://github.com/omerreish-lgtm/secretary-system --skill project-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting a new project often involves unstructured ideas and brain dumps, making it hard to define clear goals, scope, and success criteria. This ambiguity can lead to scope creep, wasted effort, and unclear outcomes.

Core Features & Use Cases

  • Structured Brief Generation: Transforms raw ideas into a comprehensive project brief (problem, goals, scope, milestones, deliverables, success criteria).
  • Interactive Refinement: Guides you through clarifying questions to ensure the brief accurately reflects your vision and captures all critical details.
  • Standardized Project Definition: Ensures all key elements of a project are captured in a consistent, easy-to-understand format.
  • Use Case: You have a new project idea for an AI strategy for your department. Use this skill to quickly generate a formal project brief, complete with problem statement, goals, and milestones, ready for stakeholder review and approval.

Quick Start

Create a new project brief for my AI strategy idea. Define the project for the new marketing campaign.

Frequently Asked Questions about project-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn unstructured project ideas into a structured brief?

A structured brief transforms raw ideas into a formatted document with defined problem statements, goals, scope, milestones, and success criteria. This skill guides you through clarifying questions to convert brainstorming notes and brain dumps into an actionable project definition ready for stakeholder review.

What should a project brief include to prevent scope creep?

A comprehensive project brief captures problem statement, goals, deliverables, scope boundaries, milestones, and success criteria in a standardized format. Defining these elements upfront clarifies expectations and reduces ambiguity that leads to scope creep and wasted effort.

Can I refine my project brief iteratively after the initial generation?

Yes, the skill supports interactive refinement through clarifying questions at checkpoints. You can iteratively adjust your brief to ensure it accurately reflects your vision and captures all critical details before finalizing for handoff.

How do I prepare a project brief for stakeholder approval?

Generate a structured brief from your project idea, then review and refine it through interactive checkpoints. The standardized format ensures all key elements are present and consistent, making it ready to export and present for stakeholder review and approval.

What's the difference between a brain dump and a formal project brief?

A brain dump is unstructured notes and scattered ideas; a formal brief organizes those ideas into defined sections: problem, goals, scope, deliverables, milestones, and success criteria. This structure eliminates ambiguity and enables clear communication across teams.

When should I create a project brief—at the start or after planning?

Create a project brief at project initiation to convert raw ideas into a standard definition. Applying it early enables iterative refinement and ensures alignment before detailed planning, preventing rework and miscommunication downstream.