task▌
26 indexed skills · max 10 per page
parallel-task
am-will/codex-skills · Productivity
Orchestrates parallel execution of dependent tasks across multiple subagents using markdown plan files. \n \n Parses task dependencies from plan markdown and launches unblocked tasks in parallel waves, ensuring correct execution order \n Provides subagents with structured task context including descriptions, acceptance criteria, validation steps, and dependency information \n Enforces test-driven development (RED phase first) with fallback to documented non-testable verification for tasks that d
parallel-task-spark
am-will/codex-skills · Productivity
Orchestrate parallel development tasks with dependency management and test-driven validation. \n \n Parses markdown plan files to extract task definitions, dependencies, and acceptance criteria, then launches unblocked tasks in parallel waves using Sparky subagents \n Enforces test-driven development (RED phase first) for testable tasks, with fallback to documented non-testable verification (manual, static, or runtime checks) \n Manages task dependencies automatically, blocking tasks until their
ln-302-task-replanner
levnikolaevich/claude-code-skills · Productivity
ln-302-task-replanner
lark-task
larksuite/cli · Productivity
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md,其中包含认证、权限处理
no-task-output
parcadei/continuous-claude-v3 · Productivity
Never Use TaskOutput \n TaskOutput floods the main context window with agent transcripts (70k+ tokens). \n Rule \n NEVER use TaskOutput tool. Use Task tool with synchronous mode instead. \n Why \n \n TaskOutput reads full agent transcript into context \n This causes mid-conversation compaction \n Defeats the purpose of agent context isolation \n \n Pattern \n # WRONG - floods context\n Task(run_in_background=true)\n TaskOutput(task_id=\"...\") // 70k tokens dumped\n \n # RIGHT - isolated context
task-coordination-strategies
wshobson/agents · Productivity
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with structured task descriptions. \n \n Provides four decomposition strategies: by architectural layer, functional component, cross-cutting concern, or file ownership to parallelize work effectively \n Includes dependency graph patterns (independent, sequential, diamond) with principles for minimizing chain depth and identifying critical paths \n Offers task description template covering objective, owned files, r