Facts

Give a capable engineer a terse, jargon-free 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.

backnotprop b1e9605 2 files · 1.4 KB Updated

File contents

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. Every fact must be terse, direct, and stated without jargon. Assume I am new here, but am a capable engineer: do not use sloganese or chiasmus, be clear&direct and as minimally verbose as possible (concise but coherent).

subject scope pertains to whatever has been in discussion/planning or just built in recent efforts.

backnotprop/bro-skills/tree/main/skills/facts commit b1e96054e2

Frequently asked questions

npx skillmds@latest add backnotprop/facts