Run any Skill in Manus with one click

textbundler-task-dev

Stars5

Forks0

UpdatedFebruary 14, 2026 at 10:13

TextBundler task implementation workflow. Auto-activates when a developer wants to implement, continue, or work on spec tasks (TASK-001 through TASK-021). Use when the user says things like "implement TASK-X", "work on the next task", "start task", "pick up where we left off", "what task is next", or references any TASK-NNN by ID. Also activates for general implementation work on the TextBundler extension pipeline modules (extraction, conversion, packaging, wiring). Integrates with OpenSpec workflows via /prompts:opsx- commands.

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

textbundle

textbundle/textbundler-extension

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

2 files

SKILL.md

readonly

name	textbundler-task-dev
description	TextBundler task implementation workflow. Auto-activates when a developer wants to implement, continue, or work on spec tasks (TASK-001 through TASK-021). Use when the user says things like "implement TASK-X", "work on the next task", "start task", "pick up where we left off", "what task is next", or references any TASK-NNN by ID. Also activates for general implementation work on the TextBundler extension pipeline modules (extraction, conversion, packaging, wiring). Integrates with OpenSpec workflows via /prompts:opsx- commands.
metadata	{"agent":"developer"}

Implement the specified task (or determine the next task) from docs/SPEC.md Section 7.2.

Follow the TDD workflow and task execution procedure defined in .codex/agents/developer.md.

Critical path: 001 -> 003 -> 004 -> 011 -> 004a -> 012a -> 012b -> 015 -> 018b -> 018c -> 020.

OpenSpec integration: use /prompts:opsx-apply for changes, /prompts:opsx-new or /prompts:opsx-ff to create changes, /prompts:opsx-verify before archiving, /prompts:opsx-archive when complete.

More from this repository

same repository

wxt-docs

textbundle/textbundler-extension

Answer questions about WXT (Web Extension Tools) framework by searching local vendor documentation. Use when the user asks "/wxt-docs <question>" or invokes this skill with a question about how WXT handles manifest conversion, content scripts, background scripts, entrypoints, MV2/MV3 differences, permissions, configuration, or any other WXT behavior. Spawns a fast haiku subagent to search the docs and return the answer.

2026-02-205

textbundler-orchestrator

textbundle/textbundler-extension

Full task lifecycle orchestrator for TextBundler. Auto-activates when the user wants to run the complete develop-review-fix-merge cycle for a spec task or OpenSpec change. Use when the user says "run the next task", "orchestrate TASK-X", "orchestrate change X", "implement and review", "full cycle", "next", "run the change", "implement configurable-figure-table-defaults", or wants hands-off task execution with automated code review and iterative fixes. Manages feature branches, spawns developer and reviewer subagents, tracks review feedback in COMMENTS.md, and merges to main when all findings are resolved.

2026-02-165

textbundler-reviewer

textbundle/textbundler-extension

Code reviewer for TextBundler feature branches. Auto-activates when the user asks to review a branch, review a PR, review code, check a feature branch, or says "review", "code review", "check the branch", "review task-NNN", "review the change branch". Supports both SPEC.md task branches and OpenSpec change branches. Produces a structured COMMENTS.md with APPROVE / REQUEST CHANGES / REJECT verdict. Has veto power over merges.

2026-02-165

textbundler-task-dev

textbundle/textbundler-extension

TextBundler task implementation workflow. Auto-activates when a developer wants to implement, continue, or work on tasks from SPEC.md or OpenSpec changes. Use when the user says things like "implement TASK-X", "work on the next task", "start task", "pick up where we left off", "what task is next", references any TASK-NNN by ID, or names an OpenSpec change to implement. Also activates for general implementation work on the TextBundler extension pipeline modules (extraction, conversion, packaging, wiring). Integrates with OpenSpec workflows via /opsx: commands.

2026-02-165

textbundler-orchestrator

textbundle/textbundler-extension

Full task lifecycle orchestrator for TextBundler. Auto-activates when the user wants to run the complete develop-review-fix-merge cycle for a spec task. Use when the user says "run the next task", "orchestrate TASK-X", "implement and review", "full cycle", "next", or wants hands-off task execution with automated code review and iterative fixes. Manages feature branches, spawns developer and reviewer subagents, tracks review feedback in COMMENTS.md, and merges to main when all findings are resolved.

2026-02-145

textbundler-reviewer

textbundle/textbundler-extension

Code reviewer for TextBundler feature branches. Auto-activates when the user asks to review a branch, review a PR, review code, check a feature branch, or says "review", "code review", "check the branch", "review task-NNN". Produces a structured COMMENTS.md with APPROVE / REQUEST CHANGES / REJECT verdict. Has veto power over merges.

2026-02-145

name	textbundler-task-dev
description	TextBundler task implementation workflow. Auto-activates when a developer wants to implement, continue, or work on spec tasks (TASK-001 through TASK-021). Use when the user says things like "implement TASK-X", "work on the next task", "start task", "pick up where we left off", "what task is next", or references any TASK-NNN by ID. Also activates for general implementation work on the TextBundler extension pipeline modules (extraction, conversion, packaging, wiring). Integrates with OpenSpec workflows via /prompts:opsx- commands.
metadata	{"agent":"developer"}

Implement the specified task (or determine the next task) from docs/SPEC.md Section 7.2.

Follow the TDD workflow and task execution procedure defined in .codex/agents/developer.md.

Critical path: 001 -> 003 -> 004 -> 011 -> 004a -> 012a -> 012b -> 015 -> 018b -> 018c -> 020.