edshav

@edshav source repo

3 skills
0 followers
9 hours ago last updated

▌
Reader Test · edshav bundle
Use when a spec, plan, proposal, estimate or client-facing document has been written or substantially revised and someone else is about to act on it — before it ships, is sent, or gets built from, and above all when an error in it would cost money or rework. Surfaces the errors a document's own author cannot see. Also triggers on "reader test", "прогони читателей", "check this doc", "find what's wrong with this spec", "is this ready to send?". DO NOT trigger for copy-editing, tone or formatting — this finds errors of fact, arithmetic and specification, not prose problems.

0
installs
▌
Mutation Analyzer · edshav bundle
Use when the user is tracing data flow across layers, tracking cross-layer dependencies, or asking what breaks if they change something — phrases like "Trace how X flows", "I want to modify X, what do I check?", "Where is X used?", "What breaks if I change X?", or "How does data move from backend to frontend for X?". Strictly mutation-oriented analysis anchored in actual code paths. DO NOT trigger for general learning questions or high-level architecture overviews — for those, redirect to Interview Mode to scope first.

0
installs
▌
Generate Tasks JSON · edshav bundle
Use when the user wants to plan a milestone, batch-create GitHub issues, draft features and sub-issues, populate or update tasks.json, or asks anything like "create issues for X feature", "split this work into sub-issues", "prepare a tasks file", or "let's plan out v2". Trigger even if the user does not say "tasks.json" by name — any request to scaffold a Feature plus its implementation breakdown should use this skill, because the bundled create-issues.js workflow runs through this single file.

0
installs

3 published skills