using-long-task

IF A PHASE SKILL APPLIES, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this.

LANGUAGE RULE: You MUST respond to the user in Chinese (Simplified). All generated documents, reports, and user-facing output must be written in Chinese. Skill names, code identifiers, and JSON field names remain in English.

How to Access Skills

Use the Skill tool to invoke skills by name (e.g., long-task:long-task-work). When invoked, the skill content is loaded and presented to you — follow it directly. Never use the Read tool on skill files.

Phase Detection

Check project state and invoke the corresponding skill:

digraph phase_detection {
    "Session Start" [shape=doublecircle];
    "bugfix-request.json exists?" [shape=diamond];
    "increment-request.json exists?" [shape=diamond];
    "feature-list.json exists?" [shape=diamond];
    "All active features passing?" [shape=diamond];
    "Design doc (*-design.md) in docs/plans/?" [shape=diamond];
    "ATS doc (*-ats.md) in docs/plans/?" [shape=diamond];
    "UCD doc (*-ucd.md) in docs/plans/?" [shape=diamond];
    "SRS doc (*-srs.md) in docs/plans/?" [shape=diamond];
    "docs/rules/ populated?" [shape=diamond];
    "Source files > 3 AND commits >= 5?" [shape=diamond];
    "Invoke long-task:long-task-hotfix" [shape=box style=filled fillcolor=orange];
    "Invoke long-task:long-task-increment" [shape=box style=filled fillcolor=plum];
    "Invoke long-task:long-task-requirements" [shape=box style=filled fillcolor=lightyellow];
    "Run codebase-scanner then long-task:long-task-requirements" [shape=box style=filled fillcolor=wheat];
    "Invoke long-task:long-task-ucd" [shape=box style=filled fillcolor=lightorange];
    "Invoke long-task:long-task-design" [shape=box style=filled fillcolor=lightblue];
    "Invoke long-task:long-task-ats" [shape=box style=filled fillcolor=lightskyblue];
    "Invoke long-task:long-task-init" [shape=box style=filled fillcolor=lightyellow];
    "Invoke long-task:long-task-work" [shape=box style=filled fillcolor=lightgreen];
    "Invoke long-task:long-task-st" [shape=box style=filled fillcolor=lightcoral];

    "Session Start" -> "bugfix-request.json exists?";
    "bugfix-request.json exists?" -> "Invoke long-task:long-task-hotfix" [label="yes"];
    "bugfix-request.json exists?" -> "increment-request.json exists?" [label="no"];
    "increment-request.json exists?" -> "Invoke long-task:long-task-increment" [label="yes"];
    "increment-request.json exists?" -> "feature-list.json exists?" [label="no"];
    "feature-list.json exists?" -> "All active features passing?" [label="yes"];
    "All active features passing?" -> "Invoke long-task:long-task-st" [label="yes"];
    "All active features passing?" -> "Invoke long-task:long-task-work" [label="no"];
    "feature-list.json exists?" -> "ATS doc (*-ats.md) in docs/plans/?" [label="no"];
    "ATS doc (*-ats.md) in docs/plans/?" -> "Invoke long-task:long-task-init" [label="yes"];
    "ATS doc (*-ats.md) in docs/plans/?" -> "Design doc (*-design.md) in docs/plans/?" [label="no"];
    "Design doc (*-design.md) in docs/plans/?" -> "Invoke long-task:long-task-ats" [label="yes"];
    "Design doc (*-design.md) in docs/plans/?" -> "UCD doc (*-ucd.md) in docs/plans/?" [label="no"];
    "UCD doc (*-ucd.md) in docs/plans/?" -> "Invoke long-task:long-task-design" [label="yes"];
    "UCD doc (*-ucd.md) in docs/plans/?" -> "SRS doc (*-srs.md) in docs/plans/?" [label="no"];
    "SRS doc (*-srs.md) in docs/plans/?" -> "Invoke long-task:long-task-ucd" [label="yes"];
    "SRS doc (*-srs.md) in docs/plans/?" -> "docs/rules/ populated?" [label="no"];
    "docs/rules/ populated?" -> "Invoke long-task:long-task-requirements" [label="yes"];
    "docs/rules/ populated?" -> "Source files > 3 AND commits >= 5?" [label="no"];
    "Source files > 3 AND commits >= 5?" -> "Run codebase-scanner then long-task:long-task-requirements" [label="yes (brownfield)"];
    "Source files > 3 AND commits >= 5?" -> "Invoke long-task:long-task-requirements" [label="no (greenfield)"];
}

Detection rules: 0. Check bugfix-request.json in project root → if exists → long-task-hotfix (HIGHEST priority) Note: If both bugfix-request.json AND increment-request.json exist, hotfix runs first; increment-request.json is preserved and processed next session.

1. Check increment-request.json in project root → if exists → long-task-increment
2. Check feature-list.json in project root → if exists:
   • Run python scripts/check_st_readiness.py feature-list.json — if exit 0 (all active features passing, excludes deprecated) → long-task-st
   • Otherwise (some active features failing) → long-task-work
3. Check docs/plans/*-ats.md → if any match → long-task-init (ATS done, proceed to init)
4. Check docs/plans/*-design.md → if any match → long-task-ats (Design done, proceed to ATS)
5. Check docs/plans/*-ucd.md → if any match → long-task-design (UCD done, proceed to design)
6. Check docs/plans/*-srs.md → if any match → long-task-ucd (SRS done, UCD next; if no UI features the UCD skill auto-skips to design)
7. Otherwise → check codebase conventions: a. Check docs/rules/ — if exists AND contains ≥1 .md file (beyond a greenfield stub) → long-task-requirements (rules already scanned) b. Check for existing source files (brownfield heuristic): count source files (*.py, *.js, *.ts, *.java, *.c, *.cpp, *.go, *.rs, etc.) excluding .git/, node_modules/, venv/, dist/, build/; and check git rev-list --count HEAD
   • If source files > 3 AND git commits ≥ 5 → run codebase-scanner (see Phase 0-pre below) → then long-task-requirements
   • Else (greenfield) → create docs/rules/README.md stub ("Greenfield — no conventions to extract") → long-task-requirements

Skill Catalog

Phase Skills (invoke ONE based on detection above)

Standalone Skills (invoke independently — no pipeline dependency)

Discipline Skills (invoked by long-task-work as sub-skills — do NOT invoke directly)

Meta Skills (invoked conditionally by phase skills — do NOT invoke directly)

Key Files (shared contract)

Red Flags

These thoughts mean STOP — you're rationalizing:

Skill Priority

1. Phase skill first — determines the entire session workflow
2. Discipline skills second — invoked by Worker in strict order (tdd → quality → st-case → review)
3. On error — follow systematic-debugging approach in skills/long-task-work/references/systematic-debugging.md before any fix

Phase 0-pre: Codebase Convention Scan (Brownfield Only)

When detection rule 7b triggers (brownfield project, no existing docs/rules/), execute these steps before invoking long-task-requirements:

1. Create output directory: mkdir -p docs/rules/

2. Detect language & framework: analyze file extensions and dependency manifests (package.json, requirements.txt, pom.xml, Cargo.toml, go.mod, *.csproj). Determine scan depth:

   LOC Range	Depth
   < 1,000	Lightweight (top 20 files)
   1,000–10,000	Standard (top 50 files)
   > 10,000	Deep (top 100 + all configs)

3. Dispatch codebase-scanner SubAgent:

   Agent(
     subagent_type="general-purpose",
     description="Scan codebase conventions for [project]",
     prompt="""
     Read the agent definition at: {plugin_root}/agents/codebase-scanner.md
   
     ## Scan Parameters
     - Working directory: {working_directory}
     - Primary language(s): {languages}
     - Primary framework(s): {frameworks}
     - Scan depth: {scan_depth}
     - Source file list: {file_list}
   
     Execute the full codebase scanner process per the agent definition.
     Return structured output per the Structured Return Contract.
     """
   )
   

4. Validate results: verify ≥1 output file exists in docs/rules/. If SubAgent returns BLOCKED, write minimal stubs (non-blocking — scan is best-effort).

5. User review via AskUserQuestion:

   • Present concise summary of key findings (especially 2/3方件 constraints and prohibited APIs)
   • Ask user to confirm or edit docs/rules/ files before continuing

6. Git commit: docs: add codebase convention rules

7. Invoke long-task:long-task-requirements