PazsitZ
- 3 skills
- 0 followers
- 20 hours ago last updated
- ▌ Design Doc · pazsitzProduce a design, planning, analysis, or architecture-decision document through a structured interview. Dispatches researcher subagents for codebase facts first, then interviews the user on every open fork with pros/cons and a recommendation, then writes a decision document to {docs-dir}/todo/ and stops. Use for "design doc", "planning doc", "analysis doc", "design proposal", "architecture decision", or when asked to think a change through before building it.
- ▌ Interview Me · pazsitzInterview the user relentlessly about a plan or design until shared understanding is reached. Investigates files/code/docs/issues/logs to resolve facts before asking, maps question dependencies, batches independent questions in parallel while asking branching decisions first, and gives a recommended answer for each. Use when user wants to stress-test, refine or deepen a plan, get grilled/interviewed on their design, or mentions "interview".
- ▌ Curate Learnings · pazsitz bundleClean up, prune, and consolidate the lessons and memories stores — archive lessons that were never used, merge duplicates that say the same thing, and promote proven rules into AGENTS.md or CLAUDE.md on your per-item confirmation. Use when asked to "clean up lessons", "prune lessons.md", "curate learnings", "distill memories", "the lessons index is getting long", or "are my lessons actually being used".