Results for “interviews”

Use when the user wants a full feature action plan (backend + frontend + tests) with the PWDEVIA 7-question method before any code is written — 'planejar a feature X', 'criar plano de feature', 'plan the user CRUD'. Interviews the human (max 2 rounds) and writes .planning/feat/features/{slug}/plan.md. Do NOT use to write code (feat-exec), for small 1–3 file changes (feat-quick), backend-only or UI-only scope (feat-backend / feat-frontend), tests for existing code (feat-test) or code review (feat-review).

The English summary is being prepared. Showing the original description.

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see page-cro.

The English summary is being prepared. Showing the original description.

Automate recruiting and hiring workflows in Ashby -- manage candidates, jobs, applications, interviews, and notes through natural language commands.

The English summary is being prepared. Showing the original description.

Use this skill when the user asks how to investigate a CMV accident — what to do at the scene, the first 24 hours, evidence preservation, who to call, preventability determination, ELD data preservation, dash cam review, witness interviews, working with insurance + attorney, and how to build a learning culture from incidents. Reference 49 CFR 392.7 + insurance industry best practices.

The English summary is being prepared. Showing the original description.

Structured interview and observation techniques for extracting tacit knowledge from domain experts

The English summary is being prepared. Showing the original description.

Conduct Critical Decision Method (CDM) interviews to elicit expert reasoning strategies (L3 knowledge) from practitioners about specific challenging past incidents. Use when capturing expertise for skill development, preserving knowledge before practitioner departure, building post-incident learning artifacts, or investigating decisions in complex sociotechnical systems. Outputs structured incident reconstructions with cues, decisions, alternatives considered, and counterfactual analysis suitable for distillation into skills or training material.

The English summary is being prepared. Showing the original description.

Apply cognitive task analysis to expert work that depends on perceptual cues, branching judgment, and recurring monitoring loops. Use when decomposing expert capability into agent structure, simulation design, or validation interviews. NOT for ordinary step-by-step SOP capture or simple pipelines with no tacit cue layer.

The English summary is being prepared. Showing the original description.

Interviews a request until no essential choice is left to guess, then hands the settled decisions on. Trigger on 'grill me', 'interview me before you build', 'stress-test this idea', 'ask me questions until it's clear', 'what am I missing before we start', or a vague plan, feature, prompt or skill where a wrong build costs more than questions. Or say grillwright (grill, record, resume, questionnaire — for someone else to answer, docs — check against glossary and ADRs). Builds nothing — prompts are promptwright's, skills skillwright's, agents agentwright's, game code slicesmith's, what a running agent may do gatewarden's, even asked as a grill.

The English summary is being prepared. Showing the original description.

Runs the test-first build loop (spec, plan, thin slices, failing test first, verify, commit) for a Godot 4 game in GDScript or C# first; in a TypeScript, Python or other repo when test-first, slices or a reproduce-first fix is asked for. Trigger to build or add a game feature, mechanic, stat, system or milestone, even when told to test later; to turn a spec or grill record into slices; to fix a game bug from a reproduction, one hypothesis at a time; on "write the test first", "what's the next slice", "is this slice done" or "is this milestone ready to exit"; or say slicesmith (spec, plan, slice, fix, exit). Run proof and gate rulings are godotsmith's; diff review a review tool's; repo maps researchscribe's; art pixelsmith's; audio soundsmith's; interviews grillwright's; fan-out dispatchwright's.

The English summary is being prepared. Showing the original description.

Fetch personalized daily horoscope forecasts from zodiac-today.com API based on natal chart calculations. Use when a user wants: (1) daily guidance on what activities to pursue or avoid, (2) life planning help — best days for interviews, travel, romance, important decisions, (3) energy/focus/luck/romance forecasts to optimize their schedule, (4) lucky colors and numbers for the day, (5) future date analysis for planning events, trips, or milestones (paid tiers). Triggers: horoscope, zodiac, star sign forecast, daily guidance, lucky day, best day to, astrology advice, what should I do today, is today a good day for, plan my week astrology. Required env: ZODIAC_API_KEY (hsk_ API key), ZODIAC_PROFILE_ID (birth chart profile ID). Collects sensitive PII (email, birth date, birth city) for natal chart — requires user consent.

The English summary is being prepared. Showing the original description.

Research before building — market research, user interviews, competitive landscape, concept validation, discovery, opportunity sizing. Feeds the product and innovation offices.

The English summary is being prepared. Showing the original description.

Use when coding interviews, focus groups, or open-ended responses with AI assistance, when a codebook needs building or auditing, when intercoder reliability must be computed, or when qualitative quotes need integrity checks before publication.

The English summary is being prepared. Showing the original description.