Run any Skill in Manus with one click

task-create

Stars121

Forks3

UpdatedJuly 17, 2026 at 01:14

Design and create implementation-ready Doradb task documents through deep repository research, strict RFC complexity gating, two proposal and review rounds, explicit user approval, and isolated task worktree creation. Use when planning a feature or bug fix into docs/tasks, including work sourced from backlog items or RFC phases.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jiangzhe

jiangzhe/doradb

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	task-create
description	Design and create implementation-ready Doradb task documents through deep repository research, strict RFC complexity gating, two proposal and review rounds, explicit user approval, and isolated task worktree creation. Use when planning a feature or bug fix into docs/tasks, including work sourced from backlog items or RFC phases.

Task Create Workflow

Use this skill to design a decision-complete task document before implementation. Scripts are executable; invoke them directly (no cargo +nightly -Zscript prefix).

Read references/workflow.md completely before executing this workflow.

Required Flow

Research relevant architecture and process documents, then inspect impacted code paths.
Apply the strict complexity gate and escalate program-level work to $rfc.
Run Round 1 with current-state analysis, evidence references, and materially different proposals.
Require user feedback on the recommendation.
Run Round 2 to finalize scope, interfaces, implementation details, tests, and open questions.
Require explicit user approval before writing any task document or creating its worktree.
After approval, allocate the task id from the dispatch root, create an isolated worktree from origin/main, and write the task document there.

Do not skip or reorder these gates.

Proposal Quality Gate

Include these explicit lenses in Round 1:

First-Principles Proposal
Long-Term Evolution Proposal
Original-Requirement-Fit Proposal

Recommend the best overall direction for correctness and project evolution. Do not default to the original request, and do not use effort tiers as substitutes for materially different strategic directions.

Write Boundary

Do not create draft task files before approval. After approval, write only under .worktrees/<task-id>/docs/tasks/; never fall back to the dispatch root when worktree creation fails.

Keep Implementation Notes blank during task design.

Output Quality

Ensure the resulting task document is:

Grounded in current code and documentation.
Narrow enough for one testable task.
Decision-complete for direct implementation.
Explicit about goals, non-goals, impacts, risks, and tests.
Traceable to source backlog or RFC phase inputs when applicable.

More from this repository

same repository

rfc

jiangzhe/doradb

Design and resolve RFC documents through evidence-gated multi-round workflow. Use when planning large architectural/program-level changes in docs/rfcs, enforcing goal/scope/direction clarity, explicit first-principles/long-term/original-fit proposal lenses with rationale, draft-to-formal progression, and resolve-time synchronization with task/backlog outcomes plus readiness validation.

2026-07-17121

style-audit

jiangzhe/doradb

Audit branch-diff Rust files, or explicitly requested file/directory Rust targets, for Doradb coding style using deterministic tooling and concise read-only review. Use when asked to check coding style, run a style audit/style auditor, validate task-branch Rust changes during $task-resolve, or report style violations in branch-modified files.

2026-07-17121

task-prune

jiangzhe/doradb

Inspect and optionally remove completed Doradb task worktrees and their local branches with deterministic safety checks. Use when listing cleanup candidates or pruning implemented, clean, fully pushed task worktrees from the main dispatch checkout; never delete remote branches.

2026-07-17121

task-resolve

jiangzhe/doradb

Resolve implemented Doradb task documents after code, tests, review, and behavior verification are complete. Use when running the mandatory style gate, recording implementation outcomes, managing deferred or source backlogs, refreshing task ids, and synchronizing a parent RFC phase without committing or pushing.

2026-07-17121

issue

jiangzhe/doradb

Create and list GitHub Issues with deterministic scripts. Use when validating planning-document paths, converting docs/tasks or docs/rfcs into trackable GitHub issues with required type labels and default priority handling, or listing existing issues in this repository.

2026-07-16121

backlog

jiangzhe/doradb

Manage backlog todo documents in docs/backlogs with deterministic tooling. Use when manually creating backlog items with duplicate checks, especially deferred follow-ups discovered during in-progress task/RFC work that need recoverable context, or closing/archiving backlog items with explicit reasons.

2026-03-28121

name	task-create
description	Design and create implementation-ready Doradb task documents through deep repository research, strict RFC complexity gating, two proposal and review rounds, explicit user approval, and isolated task worktree creation. Use when planning a feature or bug fix into docs/tasks, including work sourced from backlog items or RFC phases.

Task Create Workflow

Use this skill to design a decision-complete task document before implementation. Scripts are executable; invoke them directly (no cargo +nightly -Zscript prefix).

Read references/workflow.md completely before executing this workflow.

Required Flow

Research relevant architecture and process documents, then inspect impacted code paths.
Apply the strict complexity gate and escalate program-level work to $rfc.
Run Round 1 with current-state analysis, evidence references, and materially different proposals.
Require user feedback on the recommendation.
Run Round 2 to finalize scope, interfaces, implementation details, tests, and open questions.
Require explicit user approval before writing any task document or creating its worktree.
After approval, allocate the task id from the dispatch root, create an isolated worktree from origin/main, and write the task document there.

Do not skip or reorder these gates.

Proposal Quality Gate

Include these explicit lenses in Round 1:

First-Principles Proposal
Long-Term Evolution Proposal
Original-Requirement-Fit Proposal

Write Boundary

Do not create draft task files before approval. After approval, write only under .worktrees/<task-id>/docs/tasks/; never fall back to the dispatch root when worktree creation fails.

Keep Implementation Notes blank during task design.

Output Quality

Ensure the resulting task document is:

Grounded in current code and documentation.
Narrow enough for one testable task.
Decision-complete for direct implementation.
Explicit about goals, non-goals, impacts, risks, and tests.
Traceable to source backlog or RFC phase inputs when applicable.