isvlasov

Shape an idea into a concept through guided dialogue

Conducts research. Use when asked to research, investigate, explore, look into a topic, compare options, learn about an unfamiliar domain, or understand current state.

Designs workflow structure. Use when planning a workflow, choosing which phases to include, or selecting a workflow pattern for a task.

Creates the standard project file structure for a software project. Use when starting a new software project, initialising project files, or setting up a project workspace before architecture and decomposition begin.

Converts an approved ARCHITECTURE.md into an implementation roadmap of isolated, dependency-ordered chunks. Use when architecture has been approved and work must be decomposed before implementation begins.

Extracts genuine value from a subject and frames it so the right audience recognises it. Use when producing LinkedIn posts, pitch narratives, cover letters, proposals, case studies, or positioning statements. Not for general writing guidance, negotiation, or copywriting templates.

Session handover — end a session by systematically updating project state files for continuity. Use this when the session is ending, the user asks for a "handover", or when significant progress needs to be recorded.

Reviews code. Use when reviewing code implementations, assessing code quality, running a security review, checking spec or design system compliance, or conducting an end-of-build whole-project review against PRD success criteria.

Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.

Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — including well-known ones like React, Next.js, Prisma, Django, or Spring Boot. Use for API syntax, configuration, version migration, setup, and library-specific debugging. Use even when you think you kn

Enriches implementation roadmap chunks with acceptance criteria, pattern references, and contextual notes. Use after decomposing-work has produced the structural roadmap and before planning-software creates the orchestration plan. Does not modify chunk structure or dependencies.

Collects research sources with quality evaluation. Use when gathering or finding sources, building a source library, searching for academic papers, or performing RADAR assessment.