Back to list
knowns-dev

knownstaskreopen

by knowns-dev

AI-first CLI for task management and documentation. Link docs in tasks, AI reads context automatically. Stop repeating patterns every session. Built-in time tracking, MCP Server, Web UI. Know what your team knows.

66🍴 13📅 Jan 23, 2026

SKILL.md


name: knowns.task.reopen description: Use when reopening a completed task to add new requirements, fix issues, or extend functionality

Reopening Tasks

Reopen completed tasks properly with time tracking and requirement documentation.

Announce at start: "I'm using the knowns.task.reopen skill to reopen task [ID]."

Core principle: DOCUMENT WHY THE TASK IS REOPENED.

The Process

Step 1: View Current Task State

knowns task $ARGUMENTS --plain

Verify:

  • Task is currently done
  • Understand what was implemented
  • Review implementation notes

Step 2: Reopen and Start Timer

# Set back to in-progress
knowns task edit $ARGUMENTS -s in-progress

# Start timer (REQUIRED)
knowns time start $ARGUMENTS

Step 3: Document Reopen Reason

knowns task edit $ARGUMENTS --append-notes "🔄 Reopened: <reason>"

Common reasons:

  • User requested changes
  • Bug found in implementation
  • New requirements added
  • Missed acceptance criteria

Step 4: Add New Requirements

# Add new acceptance criteria
knowns task edit $ARGUMENTS --ac "New requirement 1"
knowns task edit $ARGUMENTS --ac "Fix: issue description"

Step 5: Update Plan (if needed)

knowns task edit $ARGUMENTS --plan $'Previous plan + new steps:
1. Original step (done)
2. Original step (done)
3. NEW: Address new requirement
4. NEW: Fix reported issue'

Present updated plan and WAIT for approval.

Step 6: Implement and Complete

Follow normal task completion flow:

# Check new ACs as completed
knowns task edit $ARGUMENTS --check-ac <new-index>
knowns task edit $ARGUMENTS --append-notes "✓ Done: new requirement"

# Stop timer
knowns time stop

# Mark done again
knowns task edit $ARGUMENTS -s done

When to Reopen vs Create New Task

Reopen ExistingCreate New Task
Small fix/changeMajor new feature
Related to original workUnrelated work
Same context neededDifferent context
Quick additionSignificant scope

Rule of thumb: If it takes < 30 mins and relates to original task, reopen. Otherwise, create new task with reference.

Creating Follow-up Task Instead

knowns task create "Follow-up: <description>" \
  -d "Related to @task-$ARGUMENTS" \
  --ac "New requirement"

Remember

  • Always document reopen reason
  • Start timer when reopening
  • Add new AC for traceability
  • Stop timer when done
  • Consider if new task is more appropriate

Score

Total Score

75/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

+5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon