“dma”的搜索结果

Use when the user says "create roadmap", "show roadmap", or "execute roadmap". Creates, reads, and manages roadmap files with phase tracking.

中文简介正在准备中。当前显示原文说明。

Create or update a product roadmap, compare priorities, and adjust timelines. Organize initiatives by timeframe or goals, show owners and dependencies, and summarize what changed alongside risks and team capacity limits.

中文简介正在准备中。当前显示英语简介。

• Adding an initiative and deciding what to postpone
• Reprioritizing after customer feedback
• Assessing the impact of a dependency delay

Review product roadmaps through six questions about customer needs, retention, priorities, and tradeoffs. Produce a recommendation on what to ship, refine, or stop, with measurable criteria for reassessing the decision after 90 days.

中文简介正在准备中。当前显示英语简介。

• Reviewing a quarterly product roadmap
• Deciding whether to build or discontinue a feature
• Assessing product demand through retention

Create an SEO strategy for a new or existing website, tailored to its industry, competitors, goals, and resources. Produce a site structure, content calendar, technical priorities, and phased implementation roadmap with measurable targets.

中文简介正在准备中。当前显示英语简介。

• Plan SEO before launching a website
• Review an existing site's strategy against competitors
• Design URL structure and internal links

Reviews deferred project tasks alongside their descriptions and supporting files, then lets users promote, keep, or remove each item. Promoted tasks join the active milestone with updated phase numbers and roadmap entries.

中文简介正在准备中。当前显示英语简介。

• Review deferred tasks and their supporting materials
• Move selected backlog items into the active milestone
• Remove outdated backlog items

Plan an existing development phase around a small, usable feature. Define who needs it and why, check whether the work should be split, update ROADMAP.md, and hand off to phase planning.

中文简介正在准备中。当前显示英语简介。

• Reframe an existing phase around a minimum usable feature
• Clarify the user, desired action, and purpose
• Split an oversized story into multiple phases

Assess Docker, containerd, and Podman environments for weaknesses that could expose the host system. The skill organizes checks for excessive permissions, exposed runtime sockets, and known vulnerabilities, alongside indicators defenders can monitor.

中文简介正在准备中。当前显示英语简介。

• Assessing container isolation
• Reviewing permissions and exposed runtime sockets
• Checking known runtime vulnerabilities

Check whether a Dynamo deployment is ready for disaggregated serving, where input processing and token generation run separately. Read-only probes inspect transport settings, GPU networking capabilities, and NIXL transfer-test readiness, then report gaps and next steps.

中文简介正在准备中。当前显示英语简介。

• Check communication readiness after deployment
• Inspect transport setup before benchmarking
• Investigate suspected communication bottlenecks

Create a phased roadmap for splitting a monolithic application into separate services. Assess current progress, prioritize work by risk, value, and dependencies, and produce milestones, estimated effort, acceptance criteria, and progress reports.

中文简介正在准备中。当前显示英语简介。

• Planning a migration from a monolith to separate services
• Prioritizing components for extraction
• Defining phase milestones and completion criteria

Raw verbs inside DOCA Core (doca-verbs): direct control of QP, CQ, PD, SRQ and address-handle objects through doca_verbs_context, doca_verbs_qp_create / doca_verbs_qp_modify and doca_verbs_cq_create, porting libibverbs code into DOCA Core, or a QP attribute, opcode or WR flag the doca-rdma task API does not expose. Trigger on "raw QP attribute the task API does not expose", "porting libibverbs code", "IO_FAILED on WR submit", "QP state transition rejected", or "attach a congestion-control group", even without naming doca-verbs. Its first job is to route MOST users back up to doca-rdma, doca-eth or doca-rmax. Covers CC-group and Ethernet SQ/RQ primitives, capability queries via doca_verbs_query_device, and DOCA_ERROR_* from doca_verbs_* calls. Refuse and route elsewhere for ordinary doca-rdma / doca-eth / doca-rmax workloads, DOCA install, Core internals, and general libibverbs theory.

中文简介正在准备中。当前显示原文说明。

Use this skill for hands-on DOCA GPI programming — wiring a GPU-Packet-Initiator context so a CUDA kernel drives RDMA queues directly from GPU memory without host CPU mediation. Covers picking GPI vs doca-gpunetio, the doca_gpi / domain / channel object model, the GPU-side handle handoff (doca_gpu_gpi_channel*), attaching GPU memory to a GPI domain, the domain and channel attribute objects, and debugging DOCA_ERROR_* from doca_gpi_* calls. Trigger even when the user does not explicitly mention "DOCA GPI" — implicit phrasings include "my CUDA kernel needs to post RDMA directly from GPU memory", "DOCA_ERROR_* from doca_gpi_gpu_channel_get", "how do I hand a GPU handle to my CUDA kernel", "how many channels can a GPI domain hold", or "GPU kernel driving RDMA without the host CPU on the path". Refuse and route elsewhere for the doca-gpunetio Send/Receive surface, the doca-rdma queue lifecycle, DPA-side initiation (doca-rdmi), or the CUDA programming model — those belong to other skills.

中文简介正在准备中。当前显示原文说明。

Rigorous, defensible email-spoofability verdict and SPF supply-chain risk analysis computed from published DNS alone. Deepens the record-level SPF/DMARC/DKIM/BIMI/MTA-STS/DNSSEC fetch recipes in the offensive-osint arsenal (§16.14) with the reasoning that section doesn't do: a priority-ordered composite verdict for whether an attacker can actually land header-From-spoofed mail in an inbox, and by which vector (exact-domain vs subdomain) — grounded in the single most-misunderstood distinction in email security: the envelope MAIL FROM that SPF authenticates vs the visible header From: that only DMARC governs. Explains precisely why SPF -all/~all alone is NOT spoof-proof without DMARC enforcement, and why SPF +all bypasses DMARC even under p=reject pct=100. Covers RFC 7208 §4.6.4's 10-DNS-lookup / 2-void-lookup PermError fail-open condition with a runnable stdlib-only lookup-counter script, plus the SPF-include-takeover supply-chain vector (an attacker re-registering a dead include inherits SPF-pass authority over the victim domain) with strict transient-vs-NXDOMAIN discrimination discipline so a temporary SERVFAIL is never mistaken for a takeover lead. Fully passive: DNS TXT reads only, no mail sent, no RCPT TO probe, no API keys. Use when auditing a domain's real spoofing resistance (not just its published records), explaining to a client why 'we have SPF -all' does not mean they're covered, investigating an SPF PermError or an unusually long include chain, evaluating a dead SPF include as a takeover lead, or writing a defensible spoofability finding for a deliverable.

中文简介正在准备中。当前显示原文说明。

Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.

中文简介正在准备中。当前显示原文说明。

Translate one internal roadmap into audience-appropriate formats with confidence-band discipline. Use when preparing a roadmap readout, tailoring it for an exec, customer, eng, or sales audience, or auditing over-promise risk.

中文简介正在准备中。当前显示原文说明。

Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.

中文简介正在准备中。当前显示原文说明。

Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".

中文简介正在准备中。当前显示原文说明。

Drive the ENTIRE tdmcp roadmap-to-1.0 to completion as a resumable, wave-by-wave campaign — Milestone 4 (generative-AI bridge wave), Milestone 5 (mixer scene arming), and the v1.0 consolidation gates G1–G6 — routing each class of work to the right existing sub-harness. Use whenever the user wants to "implement everything / all the milestones / the whole roadmap / finish the road to 1.0", run the next milestone, close the consolidation gates, or build a long autonomous campaign across M4/M5/G1–G6. ALSO use for every follow-up: continue/resume the roadmap campaign, run the next wave, re-run a failed wave, fold in QA results, check campaign status, re-prioritize, or scope to one milestone/gate. This is the CAMPAIGN layer ABOVE tdmcp-pipeline / tdmcp-feature-lead / tdmcp-backlog-campaign — it sequences across MULTIPLE sub-harnesses (tools, mixer, coverage, docs, bridge, recipes, submission), which the generic backlog-campaign does not. For a SINGLE feature use tdmcp-pipeline; for one tool-shaped backlog file use tdmcp-backlog-campaign. Simple questions can be answered directly.

中文简介正在准备中。当前显示原文说明。

Build an organic-traffic operating system for any site or app: a multi-phase, resumable engine that plans and ships a BATCH ROADMAP of landing pages (use-cases, playbooks, /for/ pages, roundups) on top of real keyword research, with a persistent phase tracker. Use when the user says 'SEO machine', 'build organic traffic', 'rank on Google', 'we need traffic', 'SEO roadmap', 'batch of pages', 'pages roadmap', or 'build an SEO engine'. Distinct from `seo-audit` (one-off diagnostic) and `seo-content` (single-article writer): this skill owns the multi-page roadmap, run sequencing, page generation, internal linking, and the persistent phase tracker across the whole run. For a single alternatives or vs/comparison page, see /competitor-alternatives; for programmatic SEO templates and content at scale, see /seo-content; for off-page link building, see /off-page-seo. Resumable — every invocation continues the last run.

中文简介正在准备中。当前显示原文说明。

Detect drift in .arkhe/roadmap/ context files and regenerate them from the current codebase state. Scaffolds context directory if missing. Use when user runs /roadmap:refresh, mentions "refresh context", "update context", "init roadmap", "stale context", or "scaffold roadmap".

中文简介正在准备中。当前显示原文说明。

Create or update a strategic project roadmap with major milestones. Generates .unikit/ROADMAP.md — a high-level checklist of project goals. Use when user says "roadmap", "project plan", "milestones", "what to build next", "strategic goals", or wants to see big-picture progress. Also use when the user asks to check which milestones are done or wants to plan the overall project direction.

中文简介正在准备中。当前显示原文说明。

Propose the next dependency-ready sprint from the ALREADY-DECOMPOSED roadmap — standup's active sibling. Reads docs/roadmap-execution-plan.md + the memory backlog, computes per-task readiness from the roadmap's machine-readable status, orders with roadmap-planner's graph engine, and emits a proposed task-set (sprint-plan manifest shape) with per-feature done-criteria, excluding unready tasks and naming their unmet prerequisite. PROPOSES ONLY — the human confirms/edits before /triage routes it (typically to the `power` track). Distinct from `sprint-plan`, which decomposes a fresh vision.

中文简介正在准备中。当前显示原文说明。

Use when authoring or rewriting a roadmap in agents/roadmaps/ — phases, goal, acceptance criteria, council notes; fires even on 'write a plan for X' / 'draft a roadmap'.

中文简介正在准备中。当前显示原文说明。

Use when an approved PRD must become an executable roadmap — 'gerar roadmap do PRD', 'quebrar o PRD em épicos e features', 'cadeia de dependências', 'roadmap with dependencies' — Phase/Epic/Feature/Task with explicit dependencies, waves and critical path, validated by a deterministic checker, with an approval gate. Do NOT use for a PRD that is not approved (prd- create/prd-refine first).

中文简介正在准备中。当前显示原文说明。

Build a three slide quarterly review or roadmap presentation with a retro blue, orange, and cream palette. The self-contained HTML includes a cover, three priorities, a timeline, key performance indicators, keyboard navigation, and animated transitions.

中文简介正在准备中。当前显示英语简介。

• Presenting a quarterly review
• Sharing three priorities with a team
• Showing a roadmap alongside key performance indicators