brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
plugin-feedbackWrite development-skills feedback from observed work, or assess a report for useful simplifications.
Independent GitHub snapshot · Automated classification · Original documentation governs
produce writes docs/reports/development-skills-feedback-YYYY-MM-DD.md from the current session.
Include the task, used capabilities, observed delays or errors, evidence, and reproducible improvement ideas.
Explain decision reasons. Do not include private reasoning traces or invent token and time measurements.
ingest <report-path> treats the report as claims to verify against the current files and observed behavior.
Apply changes within the user's authorization when they fix a demonstrated problem or repeated waste.
Prefer deletion or merging. Keep project facts and avoid a universal rule for one model mistake.
Add an eval only when it can expose a meaningful regression, and tag its owning paths.
Report changes, rejected suggestions with reasons, and verification limits.