cc-feature

Coordinate feature development workflows from task validation to documentation.

Updated May 7, 2026
One-click install
npx skills add https://github.com/lgzarturo/codeconductor --skill cc-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-feature
Source: https://github.com/lgzarturo/codeconductor/tree/main/.agents/skills/cc-feature
Command: npx skills add https://github.com/lgzarturo/codeconductor --skill cc-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end feature development workflows across tasks from validation to documentation.

Core Features & Use Cases

  • Task Card validation (task-coach)
  • Technical Plan (architect)
  • Implementation (implementer)
  • Test coverage (tester)
  • Code review (reviewer)
  • Documentation (docs)

Quick Start

Describe the initial feature input to task-coach and guide the workflow through architecture, implementation, testing, review, and documentation.

Frequently Asked Questions about cc-feature

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

FAQPage Schema
How do I coordinate end-to-end feature development workflows from planning to documentation?

End-to-end feature workflows coordinate task validation, technical planning, implementation, testing, review, and documentation through structured handoffs and guardrails. This ensures a controlled, repeatable process for the complete feature lifecycle.

What is the best way to validate task cards before starting technical implementation?

Task card validation uses a task-coach phase to evaluate the initial feature input before proceeding. It ensures structured handoffs into technical planning, implementation, and testing within a controlled, repeatable process.

Can I enforce structured handoffs between architecture planning, implementation, and code review?

Structured handoffs between architecture, implementation, and code review are enforced using workflow guardrails and clear decision points. This maintains a controlled, repeatable process throughout the feature lifecycle.

Does this feature workflow tool support automated test coverage and documentation generation?

The feature workflow supports test coverage and documentation through dedicated tester and reviewer phases. It guides the process from architecture and implementation through testing, review, and final documentation generation.

When do I need a controlled, repeatable process for feature lifecycle management?

A controlled, repeatable process for feature lifecycle management is needed when coordinating complex workflows from validation to documentation. It enforces strict guardrails and clear decision points to ensure reproducible outcomes.