cc-new-feature

Orchestrates end-to-end feature development with persistent task state in .codex/tasks directories.

1.0k|109|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/doccker/cc-use-exp --skill cc-new-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-new-feature
Source: https://github.com/doccker/cc-use-exp/tree/main/.codex/skills/cc-new-feature
Command: npx skills add https://github.com/doccker/cc-use-exp --skill cc-new-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

New feature work in AI coding sessions often loses track of requirements, design decisions, and progress when sessions are interrupted or resumed. This Skill provides a structured workflow that persists task state to project-local files so features can be clarified, implemented, verified, and resumed without losing context.

Core Features & Use Cases

  • Full-lifecycle workflow: Covers requirement clarification, design decisions, step-by-step implementation, verification, and a final self-review before archiving.
  • Persistent task state: Writes task files to .codex/tasks/ using a structured template, archives completed tasks to .codex/tasks/archived/, and resumes unfinished tasks instead of restarting.
  • Status discipline: Enforces explicit states (需求中, 待开始, 进行中, 已完成) with only one active in-progress task at a time.
  • Use Case: You ask the AI to build a new filtering feature, get interrupted mid-implementation, and later say "continue the last task" — the Skill scans .codex/tasks/, finds the unfinished task file, and resumes from the recorded state.

Quick Start

Ask the AI to use cc-new-feature to plan and implement a new feature, persisting progress in the project's .codex/tasks directory.

Frequently Asked Questions about cc-new-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume an interrupted feature task in Codex?

The Skill scans the project's .codex/tasks directory for unfinished task files, ignoring the archived subdirectory. If one unfinished task exists it asks whether to continue; with multiple tasks it lists names and update times for you to choose.

How does the new feature workflow track task progress?

It writes a structured Markdown task file to .codex/tasks using a template with status, implementation plan, modified files, and verification sections. Status moves through requirement, pending, in-progress, and completed states as work advances.

When should I not use a full feature development workflow?

Avoid it for small bug fixes, pure requirement or design documents, and one-off code reviews. If you only need to record task state or an interruption point without starting implementation, use the cc-task-state skill instead.

What happens if the project .codex/tasks directory is not writable?

The Skill first attempts mkdir -p .codex/tasks/archived and routes through platform approval if a permission boundary is hit. Only after the project directory is confirmed unwritable does it fall back to ~/.codex/tasks, explicitly stating the reason.

Can multiple feature tasks be in progress at the same time?

No. The workflow enforces a single main task in the in-progress state at any moment. Other candidate features remain in requirement, pending, or to-resume states until the active task completes and is archived.