Results for “decompose”

Run a high-thoroughness end-to-end implementation loop using clean worker worktrees, per-slice planning, implementation, explicit review/fix iteration, orchestrator integration, and final commit/PR drafting. Use when the user explicitly wants a Ralph/Wiggum-style loop, autonomous multi-agent execution, a delegated feature/bugfix carried from confirmed scope through review-ready completion, or RFC-driven implementation that should be reviewed, bumped to In Progress, decomposed into phases, and executed through nested sub-loops. Supports Codex subagents by default and external CLI workers such as OpenCode when explicitly requested and available.

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

Dissect the current Git change set, treated as an epic, domain-wise and logically into cohesive parts and materialize each part in its own dedicated Git WorkTree. Use when the user calls to "dissect", "split", "break up", or "decompose" a large change set into atomic, separately committable parts.

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

Dissect the current or given task plan, treated as an epic, domain-wise and logically into cohesive parts and materialize each part as its own separate task plan. Use when the user calls to "dissect", "split", "break up", or "decompose" a large "task" or "plan".

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

Run a marketing objective to completion over hours, days, or weeks — not a single deliverable. Takes a business outcome ("40 qualified demos a month from organic by Q4", "cut blended CAC below $90", "launch the product in September"), decomposes it into work items with declared ECO floors, executes them across context windows with resumable state, and stops only when an independent gate returns SHIPPED or CLOSED. Use when the request is an outcome rather than an artifact, when work must continue in the background or across sessions, or when the user says "goal", "run this until", "keep working on", "autonomous", "long-running", "over the next month", or "get us to <number>".

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

Decompose dense codebase-wide, multi-document, PDF, and aggregation work even when the input fits the context window, following Recursive Language Models (Zhang, Kraska, Khattab, 2025). Use when the user asks to analyse all files, a whole repo, all docs, large PDFs, or to aggregate or multi-hop across scattered sources. Skip one file, one function, a single needle, or a one-page PDF conversion. Triggers: long context, context rot, large codebase, many files, all files, big document, multi-document, PDF, aggregate, summarize everything, codebase-wide, multi-hop, recursive, sub-agents, map-reduce.

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

Analyze and decompose a product topic into a text-only proposal for the repository's .pm board. Use when the user wants to pressure-test scope, size milestones, identify dependencies, or prepare exact PM board commands without writing board files.

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

Decomposes portfolio risk with factor attribution, idiosyncratic risk, and marginal contribution to risk analysis. Use when decomposing portfolio risk, attributing risk sources, or analyzing factor risk contribution.

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

Generate Claude Code native Tasks from an existing spec. Use when user says "create tasks", "generate tasks from spec", "spec to tasks", "task generation", or wants to decompose a spec into implementation tasks.

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

Analyze specifications and decompose into independent changes.

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

Generalised autonomous optimisation loop — soft RLVR for any artifact a user can measure. Use this skill whenever a user wants to iteratively improve an artifact — code, prompts, documents, configs, designs, content — by running structured experiments, evaluating results against a multi-dimensional rubric, and learning from each attempt. Triggers include: "optimise this", "keep improving until it's good", "run experiments on", "autoresearch", "iterate on this overnight", "try different approaches and pick the best", or any request implying repeated evaluate-and-improve cycles. Also use when the user wants to improve a system prompt, a data pipeline, a writing style, or any artifact where quality can be decomposed into measurable tracks. For inference optimisation tasks (model latency, throughput, quantization, GPU deployment), a* delegates the low-level tuning to AITune while maintaining quality tracking and learning.

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

Phase 3: Dependency decomposition. Only invoke when explicitly requested by the user or by the yoink orchestrator.

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

Curate tests then decompose dependencies

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

Orchestrate complex development with AUTOMATIC parallel subagent execution, continuous dispatch scheduling, dependency analysis, file conflict detection, and IOSM quality gates. Analyzes task dependencies, builds critical path, launches parallel background workers with lock management, monitors progress, auto-spawns from discoveries. Use for multi-file features, parallel implementation streams, automated task decomposition, brownfield refactoring, or when user mentions "parallel agents", "orchestrate", "swarm", "continuous dispatch", "automatic scheduling", "PRD", "quality gates", "decompose work", "Mixed/brownfield".

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

This skill should be used when the user asks to "generate tasks", "create implementation plan", "break down feature", "write agent prompts", "decompose into tasks", "create work items", or when creating agent-ready task descriptions from PRD and SDD documents.

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

"Apply the Fama-French three-factor model to decompose asset returns into market, size, and value factors. Use this skill when the user needs to explain cross-sectional return differences, evaluate fund performance beyond CAPM alpha, assess small-cap or value tilts in a portfolio, or when they ask 'why do small caps earn more', 'is value premium real', or 'what factors drive returns'.".

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

"Apply DuPont Analysis to decompose Return on Equity (ROE) into profitability, efficiency, and leverage components. Use this skill when the user needs to diagnose why ROE is high or low, compare financial performance drivers across companies, or identify which operational lever to pull — even if they say 'why is our ROE declining' or 'how do we improve returns'.".

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

"Implement matrix factorization to decompose user-item interaction matrices into latent factor representations. Use this skill when the user needs scalable collaborative filtering, latent feature discovery, or dimensionality reduction for recommendation — even if they say 'SVD recommendations', 'latent factors', or 'factorize the rating matrix'.".

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

Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.

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

Decompose large epics into sprint-ready sub-epics using 9 splitting patterns. Use this skill when: - A spec is approved and you need to break a large feature into estimable work items for engineering - You want to split an epic that is too large for a single sprint - You need sized sub-epics with story point estimates for sprint planning - You are preparing for engineering handoff and need to identify work packages

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.

Workflow orchestrator. Decomposes a task into ordered steps, finds or installs the right skill for each step, runs the chain, and offers to save it as a reusable skill.

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

Run multi-source web research with adversarial verification and produce a cited report: decomposes the question into 3-6 distinct queries (broad, specific, comparative, recency-anchored), searches and ranks sources by authority, recency, and specificity.

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

Run the current session as a senior developer (Opus) leading a configurable junior fleet. Decomposes requests into scoped tasks, dispatches junior-developer subagents in parallel, optionally runs an architect plan-review gate before dispatch, autonomously resolves escalations, optionally dispatches a doc-writer second wave after juniors complete, then integrates and gates with /test + /governance. Use when the user says "/dev-team", "run the dev team", "delegate this to the juniors", "act as the senior dev", or wants a task built by a senior-led fleet.

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

Create and own the master game design document (GAME.md — the authored one-pager plus the generated [gen] system/flow maps) and the GD-IDS.yaml facts registry — the top-level, big-picture layer of the GDD and the machine interface the code side reads. Use it to write the master spec from a concept or dialogue, import an existing GDD (a file path or URL), edit GAME.md content ("change a pillar", "rework the monetization stance", "tweak the loop stack"), pitch the game ("pitch" → PITCH.md), re-decompose the systems ("remap"), and — importantly — to add a new system to the design map ("let's add a new system", "add a crafting system to the game design", "add this to the GDD"). This is the structural, map-level layer plus GAME.md content edits. To write or fill in the detailed parameters of one existing system, use /unikit-gd-system; to apply one edit spanning several zones at once use /unikit-gd-apply; to invent a brand-new game concept use /unikit-gd-brainstorm.

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