project-long-task
Project Long Task
A structured workflow for long-running, milestone-based builds. This skill supports two modes:
- Init mode — New project: collects requirements through an interactive interview, then generates a complete documentation scaffold that guides autonomous execution from planning through implementation.
- Update mode — Existing project: collects requirements for a change through a focused interview, then
updates the existing documentation to incorporate the change. Supports three update types:
- New Feature — Adding new functionality (3-8 interview rounds)
- Bug Fix — Fixing issues that may change behavior or architecture (1-3 interview rounds)
- Change — Requirement changes, refactors, tech migrations (2-5 interview rounds)
Why this structure works
Long-running tasks fail when context drifts or the executor loses track of what's done and what's next. This workflow prevents that by separating concerns into distinct documents that each serve a clear purpose:
- A spec that never changes (what to build)
- A plan that tracks progress (what's done, what's next)
More from phlegonlabs/skills
harness-engineer-cli
>
10full-project-skill
>
4project-update
>
3project-init
>
3project-convert
>
3harnass-engineer-plan
Research an existing repository, align with the user, and generate a reviewed machine-readable execution plan. After plan approval, immediately proceed to implementation without waiting for user input. Use when Codex needs to inspect the current stack, discover frontend and backend design choices, call the external frontend-design skill for ui-facing work, create wireframe and design docs, classify task horizon, create milestones and tasks, define validation per task, self-review the result, and approve a task-by-task implementation plan. When the target repo lacks the `harnass-os/...` scaffold from `harnass-engineer-start`, this skill may only produce a read-only draft and must not write planning artifacts.
1