Claude-skill-registry faion-feature-executor

SDD feature executor: sequential task execution with quality gates, test validation.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/faion-feature-executor" ~/.claude/skills/majiayu000-claude-skill-registry-faion-feature-executor && rm -rf "$T"
manifest: skills/data/faion-feature-executor/SKILL.md
source content

Entry point:

/faion-net
— invoke this skill for automatic routing to the appropriate domain.

Feature Executor Skill

Communication: User's language. Docs/code: English.

Navigation

FileDescription
SKILL.mdThis file - overview and usage
CLAUDE.mdNavigation hub
execution-workflow.mdComplete workflow with all phases
quality-gates.mdValidation and acceptance criteria

Purpose

Execute all tasks in an SDD feature with full quality gates:

  1. Load project and feature context
  2. Ask user permission before starting YOLO execution
  3. Execute tasks sequentially via
    faion-task-YOLO-executor-opus-agent
  4. After each task: verify tests pass, coverage adequate, project runs
  5. After all tasks: code review cycle until no issues remain
  6. Move feature to
    done/

Context Discovery

Auto-Investigation

SignalCheck ForWhy
.aidocs/todo/
or
in-progress/
Feature folders with tasksFeatures ready for execution
constitution.md
Tech stack, testing requirementsProject standards
Test suite configTesting framework, coverage toolsQuality gate setup
CI/CD pipelinesAutomated test runsIntegration readiness
Feature tasks countNumber of TASK-*.md filesExecution scope estimation

Discovery Questions

questions:
  - question: "What execution mode do you prefer?"
    options:
      - label: "YOLO (autonomous)"
        description: "Full automation, no confirmations (requires permission)"
      - label: "Interactive"
        description: "Task-by-task confirmation"
      - label: "Review-only"
        description: "Review existing implementation"

  - question: "How many tasks are in this feature?"
    options:
      - label: "1-3 tasks"
        description: "Fast sequential execution"
      - label: "4-10 tasks"
        description: "Standard execution with checkpoints"
      - label: "10+ tasks"
        description: "Consider splitting feature or batching"

  - question: "What quality gates do you need?"
    options:
      - label: "All gates (L1-L6)"
        description: "Production-ready code"
      - label: "Essential (L1-L5)"
        description: "Development quality"
      - label: "Minimal (L1-L3)"
        description: "Prototype/POC quality"

Decision Tree

If you need...UseWhy
Create tasks before executionfaion-sddNo tasks in todo/ yet
Execute single taskfaion-software-developerDirect execution faster
Execute multiple dependent tasksThis skillSequential execution with quality gates
Execute independent tasksfaion-sddParallelize via SDD
CI/CD integrationfaion-devops-engineerInfrastructure tasks
Return to orchestratorfaion-netMulti-domain coordination

Quality Modes

Quality LevelGates AppliedUse Case
HighL1-L6 (all)Production code
MediumL1-L5Feature development
LowL1-L3Prototypes/POC

Quality Gates: L1=Lint, L2=Types, L3=Unit tests, L4=Integration, L5=Code review, L6=Acceptance

Error Responses

Error TypeAction
Test failureFix tests, retry task, continue others
Build failureStop execution, fix build first
Git conflictStop execution, resolve manually
Security issueStop execution, escalate to user

CRITICAL: User Permission Required

Before launching

faion-task-YOLO-executor-opus-agent
, ALWAYS ask user:

⚠️ YOLO Mode Activation

About to execute {N} tasks autonomously:
- Task 1: {name}
- Task 2: {name}
...

YOLO mode means:
- No confirmations during execution
- All file edits auto-approved
- Full autonomy until completion

Proceed with YOLO execution? [Yes/No]

Use AskUserQuestion tool to get explicit permission.

Agents Used

AgentPurpose
faion-task-executor-agent
Execute individual tasks
faion-code-agent
Code review (review mode)
faion-test-agent
Test execution and coverage analysis
faion-hallucination-checker-agent
Verify task completion claims

Input

/faion-feature-executor {project} {feature}

Examples:

/faion-feature-executor cashflow-planner 01-auth
/faion-feature-executor faion-net 02-landing-page

Parameters:

  • project
    : Project name (containing
    .aidocs/
    folder)
  • feature
    : Feature name (folder in
    .aidocs/{status}/
    )

Workflow Phases

See execution-workflow.md for complete details.

  1. Context Loading - Load constitution, spec, design, implementation plan
  2. Task Discovery - Find tasks in
    in-progress/
    and
    todo/
  3. Task Execution Loop - Execute each task with validation (tests, coverage, build)
  4. Code Review Cycle - Iterate until no issues remain
  5. Finalize - Move to
    done/
    , generate summary

Quality Gates

See quality-gates.md for validation criteria.

After each task:

  • All tests pass
  • Coverage meets threshold
  • Project builds and runs

After all tasks:

  • Code review passes
  • No critical/security issues
  • No style violations

Integration

With SDD Workflow

SPEC → DESIGN → IMPL-PLAN → TASKS → [FEATURE-EXECUTOR] → DONE
                                           ↑
                                    This skill

With Other Skills

SkillIntegration
faion-sddProvides SDD context
faion-dev-django-skillDjango-specific patterns
faion-testing-skillTest generation patterns

Version History

VersionDateChanges
1.0.02026-01-18Initial release
1.1.02026-01-23Modularized documentation

faion-feature-executor v1.1.0 Execute features with quality gates