Create a story-scoped, evidence-backed current-state analysis of an existing codebase for downstream architecture and program design. Invoke only when explicitly asked to analyze current state.
Thinking-partner skill for co-building shared understanding before action. Invoke only when the user explicitly asks to brainstorm, e.g. "brainstorm" or "let's brainstorm this". Do not invoke for ordinary requests that merely involve thinking, design, analysis, planning, or implementation.
Create a story-scoped target architecture from current-state analysis for downstream program design. Invoke only when explicitly asked to design architecture.
Create a story-scoped program design from current-state and architecture artifacts for downstream implementation planning. Invoke only when explicitly asked to design the program.
Domain companion for interface, interaction, and visual work — refocuses on the underlying user problem, infers taste from the existing product rather than a generic playbook, and explores 2–5 meaningfully distinct variants the user can see instead of prose descriptions. Pairs with the brainstorming skill, which…
Use Socratic teaching to walk through and revise an implementation plan until its load-bearing design is understood, challenged, and internally consistent.
Domain companion for product issue shaping — turns raw Sparks and project context into sequenced active and candidate epics with acceptance-oriented stories, reshapes existing epic scope, and supports repository-specific issue-tracker persistence. Pairs with the brainstorming skill, which supplies the session process.…
Explain a bounded subject from supplied source material and a comprehension objective with concise diagrams, code-shape sketches, and focused representations. Invoke only when explicitly asked to show or explain something visually.