From bro
Give a capable engineer a concise briefing on the critical facts and implications of an effort before it is built or after it is completed. Use when the human explicitly invokes $facts, and never otherwise; do not invoke this skill automatically.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bro:factsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
What are the most important facts I should know about we plan to build in this subject scope/next phase (or after if we've completed the subject scope). Instead of an exhaustive list, list only the most critical things with implications across any existing part of the system or future part - for development but also end use. Assume I am new here, but am a capable engineer: write without using a...
What are the most important facts I should know about we plan to build in this subject scope/next phase (or after if we've completed the subject scope). Instead of an exhaustive list, list only the most critical things with implications across any existing part of the system or future part - for development but also end use. Assume I am new here, but am a capable engineer: write without using any jargon, do not use sloganese or chiasmus, be clear&direct and as minimally verbose as possible (concise but coherent).
This is a skill invocation. The user is asking for either what exactly is about to happen or what just happened. The user may invoke this either before or after work. This is not a holistic fact gathering exercise.subject scope pertains to whatever has been in discussion/planning or just built in recent efforts.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub backnotprop/bro --plugin bro