npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@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-cli

Initialize the workflow in your project:

task init

Prerequisites

Task CLI relies on a Grill Me compatible skill for requirement exploration.

Recommended:

npx add-skill PJ-SBN-593844/skill-grill-me

Compatible Grill Me implementations may also work.


Usage

task init
task refresh
task doctor
task --help

After 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-review

Larger Requirement

/task-explore
    ↓
TASK_READY
    ↓
/task-implement
    ↓
/task-review

Bug Fix

/bug-explore
    ↓
BUG_READY
    ↓
/bug-fix
    ↓
/bug-review

Available 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:

  1. Clarifying requirements before coding
  2. Capturing execution context in concise briefs
  3. Executing with validation while archiving automatically in the background
  4. Reviewing work against acceptance criteria
  5. 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-explore now includes brief generation.
  • bug-explore now includes bug brief generation.
  • task-implement and bug-fix now validate the work and archive the brief automatically when complete.

That leaves these practical flows:

  • Explore only: /task-explore or /bug-explore
  • Execute: /task-implement or /bug-fix
  • Review: /task-review or /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 refresh

This 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 doctor

Task CLI does not install Grill Me automatically. Users remain free to choose any Grill Me compatible implementation.