workflow-lite-plan

Generate end-to-end implementation plans with exploration artifacts and task files.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/tcytan/tecton --skill workflow-lite-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-lite-plan
Source: https://github.com/tcytan/tecton/tree/main/.claude/skills/workflow-lite-plan
Command: npx skills add https://github.com/tcytan/tecton --skill workflow-lite-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts an ambiguous task request into a structured, multi-step implementation plan with supporting evidence, clarification prompts, and handoff-ready task artifacts to reduce back-and-forth during development.

Core Features & Use Cases

  • Multi-angle code exploration: Performs 1–4 targeted explorations to gather architecture, security, performance, and integration context, then records findings into per-angle JSON artifacts.
  • Clarification-driven planning: Aggregates clarification needs across explorations and asks up to four questions per round (multi-round until clarified or exhausted).
  • Two-layer plan output with task decomposition: Produces session-scoped artifacts including planning-context.md, plan.json, and independent .task/TASK-*.json files, then hands off to workflow-lite-execute for implementation.
  • Best-fit workflow modes: Supports auto mode (-y) to skip clarification and confirmation, and force exploration to re-check code even when prior analysis exists.

Quick Start

Ask workflow-lite-plan to produce an execution-ready plan for the repository change described in a task message, running in auto mode with clarification and confirmation skipped.

Frequently Asked Questions about workflow-lite-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is task decomposition for repository changes and when do I need it?

Task decomposition breaks an ambiguous development request into structured, multi-step implementation plans with supporting evidence. You need it when a task requires gathering architecture and security context before delegating execution.

How do I turn a vague task description into an execution-ready plan?

To turn a vague task into an execution-ready plan, run multi-angle code explorations, resolve clarification questions, and generate structured artifacts including plan.json and independent task files for downstream execution handoff.

Does this workflow planning approach support automated mode without manual confirmation?

Yes, workflow planning supports an auto mode using the -y flag to skip clarification and confirmation steps, directly generating an execution-ready plan and task artifacts without manual intervention.

Can I force code exploration to re-check the repository even if prior analysis exists?

Yes, you can force code exploration to re-check the repository context even when prior analysis artifacts exist, ensuring that your implementation plan reflects the most current codebase state.

What is the best way to plan development work requiring multi-angle code exploration?

The best way to plan such development work is orchestrating targeted explorations across architecture, security, performance, and integration angles, recording findings into per-angle JSON artifacts before generating a structured plan.

How many clarification questions can I expect during the workflow planning process?

The workflow planning process aggregates clarification needs and asks up to four questions per round, continuing in multiple rounds until all requirements are clarified or clarification options are exhausted.