Skip to content

Evaluate task-generator: Gate vs Skill #613

@rjmurillo-bot

Description

@rjmurillo-bot

Summary

Evaluate whether task-generator needs a gate (enforcement) or skill (format standardization).

Parent Story

#612 (Phase 1: Core ADR-033 Gates)

Evaluation Questions

Question If Yes If No
Is the problem "tasks aren't generated"? GATE -
Is the problem "task format varies"? SKILL -
Does task-generator agent already produce consistent TASK-NNN format? No action needed -

Investigation Steps

  1. Review recent planning artifacts in .agents/planning/
  2. Check if TASK-NNN format is consistently applied
  3. Determine if task generation is being skipped

Possible Outcomes

Outcome A: No Action Needed

If task-generator agent already produces consistent output and is being invoked appropriately, no changes needed.

Outcome B: Gate Needed

If task generation is being skipped, add gate:

# Gate: Task Generation Required
if ($Command -like "*implement*" -or $Command -like "*build feature*") {
    # Check for task breakdown before implementation
    ...
}

Outcome C: Skill Needed

If format is inconsistent, create skill with SkillCreator:

SkillCreator: create a skill for atomic task generation with TASK-NNN format

Acceptance Criteria

  • Investigation completed
  • Decision documented: GATE / SKILL / NO ACTION
  • If GATE: Implementation task created
  • If SKILL: SkillCreator invocation documented

Metadata

Metadata

Labels

agent-plannerMilestone and work package agentarea-infrastructureBuild, CI/CD, configurationarea-promptsAgent prompts and templatesarea-skillsSkills documentation and patternsenhancementNew feature or requestpriority:P2Normal: Standard enhancement or bug fix, moderate impactquestionFurther information is requestedskill-conversionAgent to skill conversion worktaskTask-level work item under a story

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions