aistack

Use when the user wants to define a spec for a feature before implementation — requirements, design, or tasks. Trigger on "write a spec for", "define requirements for", "spec out this feature", "/specs:define", or when a feature request lacks a requirements/design/tasks breakdown. Produces requirements.md, design.md, and tasks.md following spec-driven development.

Use this skill when the user wants to notes or summarize a specific context, such as a meeting, a conversation, or a document. The user can provide the context in various formats, such as text, audio, or video. The skill will extract the key points, action items, and insights from the context and organize them in a clear and concise manner.

Use this skill when the user wants to summary or organize their notes, using second-brain format, Foam for markdown.

Act as a CTO or Head of Engineering to define S.M.A.R.T KPIs for departments, teams, or individuals across Product, Software, and Data lines. Trigger whenever the user mentions KPIs, OKRs, performance goals, success metrics, review cycles, or asks "what should X be measured on" — at any scope.

Use this skill when the user is asking for a software engineering solution to a problem. This could include writing code, designing an architecture, optimizing an algorithm, or any other technical task that requires software engineering expertise. Trigger whenever the user says things like "How do I implement X?", "Can you write code for Y?", "What's the best way to design Z?", or any question that involves solving a technical problem with software.

Use this skill when the user wants to design system architecture, choose a technology stack, define coding conventions, create architecture diagrams, or map out system workflows and data flows. Trigger whenever the user says things like "design the architecture for", "what tech stack should I use", "how should I structure this system", "draw a diagram for", "design a microservice", "how should modules communicate", "what pattern should I use for", "design the database schema", "design an API", or asks how to architect any software system end-to-end. Also trigger when the user shares a PRD or project plan and wants the technical design, or asks to review/critique an existing architecture. This skill covers system design, component breakdown, tech stack selection, coding conventions, and Mermaid/PlantUML diagrams.

Use this skill when the user wants to write a Product Requirement Document (PRD) for a software project or feature. Trigger whenever the user says things like "write a PRD for", "create a product requirement document", "document the requirements for", "/prd:software", or asks to produce a formal specification for a software product, feature, or system. Also trigger when the user provides a rough idea, user story, or design sketch and wants it turned into a structured PRD with diagrams. Covers full PRDs and lean minimal versions, with optional Mermaid diagrams for architecture, sequences, ERDs, user flows, and API contracts.

Use this skill when the user wants to brainstorm product ideas, evaluate or critique an existing product concept, improve or sharpen a product idea, or rewrite product requirements (PRD, user stories, feature specs) to be clearer and more actionable. Trigger whenever the user says things like "I have an idea for a product", "what do you think of this idea", "help me improve my product concept", "write a PRD", "rewrite my requirements", "give me product ideas for X", or asks for feedback on any product-related document. Also trigger for startup ideas, SaaS concepts, feature proposals, or any discussion that involves defining what a product should do and for whom.

Use this skill when the user wants to plan a project or product delivery, break down work into structured items, or create a work breakdown structure (WBS). Trigger whenever the user says things like "plan this project", "break this down into tasks", "create a backlog for", "list the work items for", "what do we need to build X", "create epics and tasks for", "help me plan a sprint", "write a project plan", or asks how to deliver a feature, product, or system end-to-end. Also trigger when a user shares a PRD, architecture doc, or product idea and wants to know what needs to be done to ship it. This skill produces a full hierarchy: Features → Epics → Tasks → Sub-tasks, with estimates, priorities, and dependencies.

Use this skill when the user wants to implement a feature, write code for a task, translate a design or spec into working software, or review/improve an existing implementation. Trigger whenever the user says things like "implement this feature", "write the code for", "build this", "add this to the codebase", "create a function/class/module for", "translate this design into code", "refactor this", or shares a task/ticket and wants it coded. Also trigger when a user shares a design doc, architecture decision, or user story and wants working, production-grade code from it. This skill produces clean, testable, removable code with full implementation guidance.

Use this skill when the user wants a code review, wants feedback on a diff or PR, wants to know if code is production-ready, or asks "is this good?", "review this", "LGTM?", "check my PR", "what's wrong with this code", or shares a file/snippet and asks for a critique. Also trigger when the user pastes a diff and wants a structured review. Produces a structured, actionable review across correctness, security, testability, removability, readability, performance, and consistency dimensions.

Use this skill when the user wants to implement a feature, write code for a task, translate a design or spec into working software, or review/improve an existing implementation. Trigger whenever the user says things like "implement this feature", "write the code for", "build this", "add this to the codebase", "create a function/class/module for", "translate this design into code", "refactor this", or shares a task/ticket and wants it coded. Also trigger when a user shares a design doc, architecture decision, or user story and wants working, production-grade code from it. This skill produces clean, testable, removable code with full implementation guidance.