atroo/plenec
Your company brain in your coding agent: search past decisions and ADRs, plan against recorded practices, file and resolve bugs, and write what you learn back to the team.
Filing, triaging, and resolving bugs in Plenec — what makes a report actionable, the SUSPECTED confirmation lane, why resolve_bug needs a real root cause, and when to dismiss instead. Use when reporting a bug, working a triage queue, or closing one out after a fix.
Writing findings back into Plenec — when a session is worth a page, choosing between create_page, update_page, edit_page and propose_page_edit, the read-before-edit rule, ADR status transitions, and save_memory for personal context. Use after a debugging session, a design decision, or any non-obvious finding worth keeping.
How to find your way around a Plenec workspace before answering or planning — picking the right workspace, resolving short keys like ATR-T88, and choosing between search_knowledge, search_adrs, ask_brain, and the project/task views. Use whenever a question touches past decisions, architecture choices, team practices, project status, or an entity key.
The plan-review loop — read a capability, pull the engineering practices that govern the work before drafting, get human judgement on the approach, then store the plan as a PLAN page and have it judged against the workspace's practices. Use before implementing anything non-trivial, and whenever a plan needs reviewing, refining, or re-checking.
Writing the two structured product documents — a PRD for one capability, and a VISION for the product its capabilities belong to. Covers the guided conversation for each, why their headings decide how content is filed, which sections block the readiness gate, and the filing traps. Use when asked to write, review, or extend a PRD, a product spec, requirements, or a product vision.