Results for “need”

Write a structured client status report for a consulting engagement. Use when a consultant says "write my weekly status update", "I need to send a status report", "draft the client update", "what should be in the weekly report", "client wants a progress update", "help me write the RAG status", "I need to report on blockers", "end of week update to the client", or "help me communicate what's stuck". Also trigger when someone needs to communicate engagement progress, surface blockers to the client, or flag decisions that need to be made by the sponsor.

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

Decompose a business problem MECE using an issue tree, generate hypotheses, and prioritize branches for investigation. Use when a consultant says "help me structure this problem", "I need to break down this issue", "build me an issue tree", "I don't know where to start on this problem", "help me frame the problem", "what are the hypotheses here", "we need to prioritize our analysis", or "the client problem is too broad". Also trigger when describing a complex or ambiguous business problem that needs systematic decomposition before analysis begins, or when an engagement is starting and a workplan needs to be structured from a problem statement.

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

Generate advertising images automatically from a product URL + brand profile. ✅ USE WHEN: - User provides a product URL (e-commerce link) - Want automated product scraping + image generation - Have a brand profile to apply (70+ brands available) - Need funnel-stage targeting (awareness/consideration/conversion) - Want AI to auto-select model, scene, lighting based on brand ❌ DON'T USE WHEN: - User provides local product image file → use morpheus-fashion-design - Don't need a person in the image → use nano-banana-pro - Want manual control over model, scene, packs → use morpheus-fashion-design - Already have hero image, need variations → use multishot-ugc - Need video output → use veed-ugc after image generation INPUT: Product URL + brand name (optional) + funnel stage (optional) OUTPUT: PNG advertising image with product + model

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

Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.

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

Builds a DRAFT course outline from a training need and audience: learning objectives with an observable verb, condition and standard, modules in a stated order with a duration basis and sources, activities and an assessment plan aligned objective by objective, and a coverage table showing what each objective still lacks. Never sets a pass mark, declares learners competent or invents content. Use when the user asks to "build a course outline", "design a training programme for", "turn this need into modules and objectives", "draft the curriculum for this workshop" or "what should this training cover". Do not use for quiz items from finished content, use training-quiz-builder instead; for needs from surveys and manager notes, use training-needs-synthesis; for a new starter's first weeks, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Sorts a personal inbox backlog into five buckets (needs-reply-today, needs-reply-this-week, waiting-on-others, FYI, noise), writes DRAFT reply text for the messages that need an answer (up to 10 per run), and returns a dated triage report as one Markdown document. Lists moves or archives only as proposals for the user to perform, and only where a rule the user supplied says so; the agent changes nothing in the mailbox. Use when the user asks to "triage my inbox", "sort my mail", "clean up my inbox", "catch up after leave" or "what needs a reply today or this week". Do not use for a shared support queue or helpdesk export, use ticket-triage-pack instead; for what the user promised or is owed, use commitment-catcher; for one named thread, answer directly. Drafts for human review; never approves, authorises or signs off.

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

Turn a decision that needs someone else’s knowledge into a Markdown questionnaire. Clarify who will answer and what information is needed, then create prioritized questions with answer spaces for asynchronous replies or a meeting.

• Gathering information needed for a decision
• Preparing questions for an expert
• Requesting written answers before a meeting

Maintain clear business definitions and relationships in an existing glossary or CONTEXT.md. Flag unresolved meanings and refer lasting design choices to the existing architecture decision record workflow, keeping terminology separate from decision rationale and task status.

• Document business terms that need repeated explanation
• Clarify terms with multiple meanings
• Track domain interpretations awaiting confirmation

Build web search, page content retrieval, structured data extraction, and browser interactions into applications with Firecrawl. The skill guides endpoint selection, credentials, SDK or REST integration, and verification with a real request.

• Adding web search to an application
• Extracting structured data from known URLs
• Building website clicks and form filling into a workflow

Document why software decisions were made, which alternatives were considered, and what trade-offs remain. Create architecture decision records, README guidance, API documentation, and changelogs that help future contributors and AI agents understand the project.

• Recording design decisions and rejected alternatives
• Documenting public API changes
• Updating README setup instructions

Prepare a production release with checks for code quality, security, performance, accessibility, and infrastructure. Plan monitoring, gradual feature exposure, and rollback steps, then use release metrics and reliability limits to guide rollout decisions.

• Check readiness for a first production release
• Plan a gradual rollout for a major feature
• Define monitoring and post-launch checks

Turn an authorized plan into Paperclip work by deciding which tasks need separate owners, defining clear deliverables, and recording real dependencies so independent work can start and dependent work waits.

• Deciding which parts of a plan need delegation
• Assigning owners and clear deliverables
• Recording prerequisites between tasks

Build an HTML presentation for a public-transit funding proposal, covering ridership needs, the plan, risk controls, and the requested decision. The template uses bold poster-style colors and typography for city councils and public boards.

• Preparing a public-transit funding proposal
• Explaining ridership needs to a city council
• Presenting a plan with risk controls

Create an onboarding guide for new project members from a knowledge graph, a map of project components. The Markdown guide covers architecture, key concepts, a suggested learning path, important files, and areas that need extra care.

• Preparing a guide for new team members
• Organizing project architecture and key files
• Planning a codebase walkthrough

Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.

• Review accessibility coverage for shared components
• Add accessibility checks to page flow tests
• Run accessibility tests in CI

Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.

• Deciding whether a change needs a lasting decision record
• Documenting bug fixes with significant tradeoffs
• Preparing specifications for approval before implementation

Compare documentation with actual code, configuration, and commands to find outdated instructions or missing information. Produce a read-only audit with evidence, severity levels, and specific guidance on which documents need updating.

• Check documentation after a pull request
• Compare README setup steps with current code
• Find mismatches in API and environment variable docs

Create a reusable SKILL.md from research into a person’s thinking or a topic’s methods. Start with a name or a broad need, then extract mental models, decision rules, expression patterns, and limitations into a working skill.

• Creating a thinking adviser based on a named person
• Finding a suitable perspective for an unclear need
• Building a skill from personal writing and decision notes

Sort incoming email into decisions, drafted replies, and handled messages. Get a ranked list of important requests, deadlines, and past commitments, plus reply drafts based on your writing style, including from pasted email text.

• Prioritizing a backlog of unread email
• Finding deadlines and commitments in long threads
• Drafting replies in your usual writing style

Prepare for a one-on-one with a sales representative by summarizing open deals, recent activity, and available calendar and chat context. Get evidence-backed support needs, specific discussion questions, and wins to acknowledge.

• Preparing for a one-on-one with a sales representative
• Reviewing recent sales activity and deal progress
• Finding deals that need a manager's help

Turn project or team updates into a structured report for leaders and stakeholders. The skill summarizes key metrics, accomplishments, ongoing work, risks, decisions needed, and next-period priorities, with an overall assessment of whether work is on track.

• Write weekly, monthly, or quarterly progress reports
• Summarize progress against key metrics and targets
• Highlight risks and decisions needing stakeholder attention

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

• Creating signed records for production deployments
• Preserving evidence of deletions and payments
• Recording access grants for later review

Produce blog posts, articles, and guides from research through a finished draft. Build an outline from audience needs and search intent, gather sources, then refine readability, brand voice, search optimization, links, and metadata for publication.

• Researching competitors and preparing an article brief
• Writing a complete blog post or guide
• Improving search optimization and readability

Assess startup engineering operations across delivery, hiring, team structure, and production practices. Use delivery metrics, hiring conversion rates, and staffing data to identify bottlenecks, estimate candidate needs, and plan management roles and operational improvements.

• Find where development work waits before release
• Estimate candidate volume needed for hiring goals
• Review team structure and manager hiring needs