Results for “team”

Design API contracts from product flows and backend responsibilities. Use when the team needs resource models, action endpoints, request and response shapes, error handling, pagination rules, and contract clarity before implementation begins.

Score and prioritize leads based on firmographic fit and behavioral engagement signals, producing ranked tiers for sales team focus. Use when the user requests lead scoring or provides relevant inputs for this workflow.

Creates a declarative agent for Microsoft 365 Copilot by integrating an MCP server with authentication, tool selection, and configuration.

Define version control strategies for design files, component libraries, and design assets to enable team collaboration and consistency.

Read, extract, merge, split, rotate, encrypt, and create PDF files. Supports markdown-to-PDF conversion, table extraction, form filling, and OCR for scanned documents.

Plans sprints, breaks user stories into tasks, and estimates story points from BA and TechLead artifacts, producing sprint plan, task breakdown, and story point files.

Guides Git version control practices: branching strategies, commit conventions, merge vs rebase, conflict resolution, and pull request workflows for collaborative teams.

Structures an Architecture Decision Record (ADR) to capture context, decision, and consequences of significant architectural choices, ensuring decisions are documented with sufficient detail for future teams.

Build a USASpending relationship snapshot for the incumbent and buying agency on a pursuit row. Use when user needs award flows and rel counts before battlecard or teaming work — deterministic from DuckDB bulk.

Control Claude Code via MCP protocol. Trigger with "plan" to write a precise execution plan then feed it to Claude Code. Also supports direct commands, persistent sessions, agent teams, and advanced tool control.

Orchestrates teams of specialized AI agents with role-based collaboration, memory, and sequential or hierarchical execution for complex multi-step tasks.

Use when analyzing patterns across multiple incidents, bugs, failures, or successes to extract organizational learning. This skill provides procedures for synthesizing individual experiences into actionable lessons that improve team-wide practices.

Write an implementation plan from an approved architecture and MVP scope. Use when the team needs milestones, workstreams, dependency ordering, acceptance criteria, and execution sequencing that connect product intent to shippable engineering work.

Architect C2 redirectors with nginx and Apache, derive filter rules from malleable profiles, and apply OPSEC controls for resilient red-team infrastructure.

Provides structured guidance for running operations across engineering, business, and organizational contexts, including incident management, deployment checklists, rollback procedures, change management, meeting design, and operational rituals.

Backtests quantitative trading strategies across 9 engines and 25 data sources, analyzes trade journals, and runs multi-agent research teams.

Designs collaborative AI agent teams using the CrewAI framework, covering agent roles, task decomposition, crew orchestration, process types, memory systems, and event-driven flows.

Runs security audits, threat modeling, and hardening for code and infrastructure, covering OWASP checks, code review, incident response, and red/blue team exercises.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Use when sharing knowledge between agents, companies, or teams to ensure effective transfer of understanding. This skill provides procedures for structured knowledge sharing that ensures the receiver gains actionable understanding, not just information.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Use when the team needs to understand how data moves through frontend, backend, database, jobs, auth, and external integrations. Trigger on requests to map data flow, event flow, or state transitions across the system.

Use this when the team needs to define permissions, roles, membership rules, resource ownership, or action-level authorization separate from authentication choice. Trigger on requests about access models, RBAC, ABAC, tenancy, or protected operations.

Use when the team needs a strategy for validation errors, API failures, job retries, user-facing error UX, observability, or recovery behavior. Trigger on requests to design error handling across frontend, backend, and integrations.

Use when the team needs a top-level system architecture spanning frontend, backend, auth, data stores, jobs, integrations, and deployment boundaries. Trigger on requests to design the overall system or validate a proposed architecture.

Use when the team needs pricing, packaging, free-tier, trial, usage metering, or business-model guidance for a software product. Trigger on requests to design how the product should make money or control value access.

Plan the frontend application structure for a product or feature. Use when the team needs route structure, feature modules, state boundaries, design-system needs, and frontend delivery sequencing based on defined screens and flows.

Full daily team standup across all 6 verticals: Sales, Social Media, Content, SEO, Creative, and Strategy. Spawns all vertical agents in parallel, collects reports, and presents a unified standup summary. Run at 9 AM daily.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.

Install a .NET SDK into a project-local directory for safe preview testing, version pinning, or reproducible team setups without modifying the system-wide installation.

Facilitates discussion-based tabletop exercises for SOC teams to test incident response procedures, communication workflows, and decision-making under pressure without impacting production systems.

Conduct authorized physical penetration testing using tailgating, badge cloning, lock bypassing, and rogue device deployment to evaluate facility security controls.

Design, implement, test, and maintain SIEM detection rules mapped to MITRE ATT&CK across Splunk, Elastic, and Sentinel platforms.

Plan and execute authorized vishing (voice phishing) pretext calls to assess employee susceptibility to social engineering and evaluate security awareness controls.

Guide cross-functional teams through creating Jeff Gothelf's Lean UX Canvas v2 to frame business problems, surface assumptions, and define experiments.