@winton979/task-cli
v1.1.1
Published
Lightweight task workflow CLI for AI-assisted development
Readme
task-cli
Lightweight task workflow for AI-assisted development.
Designed for:
- Claude Code
- Codex CLI
- Mature projects with frequent bug fixes and small feature iterations
Task CLI provides a lightweight alternative to heavyweight spec-driven workflows by combining:
- Requirement clarification (via Grill Me)
- Brief generation
- Implementation
- Review
- Decision logging
Installation
npm install -g @winton979/task-cliInitialize the workflow in your project:
task initPrerequisites
Task CLI relies on a Grill Me compatible skill for requirement exploration.
Recommended:
npx add-skill PJ-SBN-593844/skill-grill-meCompatible Grill Me implementations may also work.
Usage
task init
task refresh
task doctor
task --helpAfter initialization, Task CLI creates the .ai/ workspace and installs workflow skills into both .claude/skills/ and .codex/skills/.
Use task refresh in existing projects to remove and reinstall only the workflow skills managed by task-cli. It does not delete your .ai briefs, internal archives, or decision log.
Use task doctor to check whether the required directories exist, whether managed skills are missing or outdated, and whether the .gitignore rules are present.
Recommended Workflow
Small Feature / Enhancement
/task-fast
↓
clarify + brief + implement + validate
↓
/task-reviewLarger Requirement
/task-explore
↓
TASK_READY
↓
/task-implement
↓
/task-reviewBug Fix
/bug-explore
↓
BUG_READY
↓
/bug-fix
↓
/bug-reviewAvailable Skills
Task Workflow
- task-fast
- task-explore
- task-implement
- task-review
Bug Workflow
- bug-explore
- bug-fix
- bug-review
Other
- decision-log
Directory Structure
.ai/
├── tasks/
│ ├── active/
│ └── archive/
│
├── bugs/
│ ├── active/
│ └── archive/
│
├── decisions/
│ └── decisions.md
│
├── .claude/skills/
└── .codex/skills/Philosophy
Task CLI is intentionally lightweight.
Instead of maintaining large specifications, it focuses on:
- Clarifying requirements before coding
- Capturing execution context in concise briefs
- Executing with validation while archiving automatically in the background
- Reviewing work against acceptance criteria
- Keeping a lightweight decision history
The goal is to improve quality without slowing down iteration speed.
Can This Be Simpler?
Yes. The main simplification is to collapse the old 4-step paths:
task-explorenow includes brief generation.bug-explorenow includes bug brief generation.task-implementandbug-fixnow validate the work and archive the brief automatically when complete.
That leaves these practical flows:
- Explore only:
/task-exploreor/bug-explore - Execute:
/task-implementor/bug-fix - Review:
/task-reviewor/bug-review - One-shot small work:
/task-fast
Upgrading Existing Projects
If a project was initialized with an older version of task-cli, run:
task refreshThis will:
- keep
.ai/tasks,.ai/bugs, and.ai/decisions - remove only these managed skills from
.claude/skills/and.codex/skills/:task-fast,task-explore,task-implement,task-review,bug-explore,bug-fix,bug-review,decision-log - reinstall the latest versions of those skills
This avoids touching unrelated custom skills in the same project.
The archive/ directories remain as internal storage. They are not separate user steps in the recommended workflow.
Before refreshing, you can inspect the current setup with:
task doctorTask CLI does not install Grill Me automatically. Users remain free to choose any Grill Me compatible implementation.
