domains / families / agent-tooling / os-big-picture

os-big-picture

separate

ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what does this thing even do", "what is stale", "what can we delete", "update the roadmap" - in any language, and whenever a session report has just been written. It keeps one file, BIG-PICTURE.md: what the product is, every feature with how far it got, which parts nobody has touched, and what is queued next. Age and wiring are measured from git; how far a feature got comes from the reports or says "not checked". Where a tracker is connected it offers to open the queue as tickets, after a yes and never before. Never invents work, never deletes code.

When to use

• where the project stands
• what's the big picture
• map the project
• what is stale
• what can we delete
• update the roadmap
• fold in session report

When not to use

• inventing work
• deleting code
• creating tickets without user confirmation

Skill page

Source