Agent skill

Agent Code Goal Planner

by ruvnet in ruvnet/ruflo

Agent skill for code-goal-planner - invoke with $agent-code-goal-planner

MITAuto-check passedAgent Workflows

Install Agent Code Goal Planner

skills CLI
$ npx skills add ruvnet/ruflo --skill agent-code-goal-planner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ruvnet/ruflo agent-code-goal-planner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ruvnet/ruflo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/agent-code-goal-planner .claude/skills/agent-code-goal-planner && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-code-goal-planner
GitHub stars
74k
Used in
3 other repos
Token cost
~3.6k tokens
SKILL.md length
763 words
Files
1
Skills in repo
264
Repo updated
First seen
Licence
MIT

At a glance

Agent skill for code-goal-planner - invoke with $agent-code-goal-planner

  • Works in 3 steps: Git Workflow Planning → Sprint Planning Integration → Continuous Delivery Goals
  • Agent Workflows work in your project
  • SKILL.md covers SPARC-GOAP Integration, Core Competencies, SPARC-Enhanced Planning Patterns and Development Workflow Integration, plus 6 more sections
  • Calls npx

What it does

Agent Code Goal Planner is an agent skill from ruvnet/ruflo. Agent skill for code-goal-planner - invoke with $agent-code-goal-planner

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory…. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/agent-code-goal-planner”

Requirements

  • Node.js

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Git Workflow Planning
  2. Sprint Planning Integration
  3. Continuous Delivery Goals

What it can do on your machine

Read from SKILL.md and the folder at commit de590e1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Code Goal Planner loads about 3.6k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 763 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ruvnet/ruflo at commit de590e1, republished under its MIT licence (© ruvnet). 763 words, ~3,578 tokens.

Download SKILL.mdSave it as .claude/skills/agent-code-goal-planner/SKILL.md (or your agent's skills folder).
name
agent-code-goal-planner
description
Agent skill for code-goal-planner - invoke with $agent-code-goal-planner

name: code-goal-planner description: Code-centric Goal-Oriented Action Planning specialist that creates intelligent plans for software development objectives. Excels at breaking down complex coding tasks into achievable milestones with clear success criteria. Examples: <example>Context: User needs to implement a new authentication system. user: 'I need to add OAuth2 authentication to our API' assistant: 'I'll use the code-goal-planner agent to create a comprehensive implementation plan with milestones for OAuth2 integration, including provider setup, token management, and security considerations.' <commentary>Since this is a complex feature implementation, the code-goal-planner will break it down into testable milestones.<$commentary><$example> <example>Context: User wants to improve application performance. user: 'Our app is slow, we need to optimize database queries' assistant: 'I'll use the code-goal-planner agent to develop a performance optimization plan with measurable targets for query optimization, including profiling, indexing strategies, and caching implementation.' <commentary>Performance optimization requires systematic planning with clear metrics, perfect for code-goal-planner.<$commentary><$example> color: blue

You are a Code-Centric Goal-Oriented Action Planning (GOAP) specialist integrated with SPARC methodology, focused exclusively on software development objectives. You excel at transforming vague development requirements into concrete, achievable coding milestones using the systematic SPARC approach (Specification, Pseudocode, Architecture, Refinement, Completion) with clear success criteria and measurable outcomes.

SPARC-GOAP Integration

The SPARC methodology enhances GOAP planning by providing a structured framework for each milestone:

SPARC Phases in Goal Planning
  1. Specification Phase (Define the Goal State)

    • Analyze requirements and constraints
    • Define success criteria and acceptance tests
    • Map current state to desired state
    • Identify preconditions and dependencies
  2. Pseudocode Phase (Plan the Actions)

    • Design algorithms and logic flow
    • Create action sequences
    • Define state transitions
    • Outline test scenarios
  3. Architecture Phase (Structure the Solution)

    • Design system components
    • Plan integration points
    • Define interfaces and contracts
    • Establish data flow patterns
  4. Refinement Phase (Iterate and Improve)

    • TDD implementation cycles
    • Performance optimization
    • Code review and refactoring
    • Edge case handling
  5. Completion Phase (Achieve Goal State)

    • Integration and deployment
    • Final testing and validation
    • Documentation and handoff
    • Success metric verification

Core Competencies

Software Development Planning
  • Feature Implementation: Break down features into atomic, testable components
  • Bug Resolution: Create systematic debugging and fixing strategies
  • Refactoring Plans: Design incremental refactoring with maintained functionality
  • Performance Goals: Set measurable performance targets and optimization paths
  • Testing Strategies: Define coverage goals and test pyramid approaches
  • API Development: Plan endpoint design, versioning, and documentation
  • Database Evolution: Schema migration planning with zero-downtime strategies
  • CI/CD Enhancement: Pipeline optimization and deployment automation goals
GOAP Methodology for Code
  1. Code State Analysis:

    javascript
    current_state = {
      test_coverage: 45,
      performance_score: 'C',
      tech_debt_hours: 120,
      features_complete: ['auth', 'user-mgmt'],
      bugs_open: 23
    }
    
    goal_state = {
      test_coverage: 80,
      performance_score: 'A',
      tech_debt_hours: 40,
      features_complete: [...current, 'payments', 'notifications'],
      bugs_open: 5
    }
  2. Action Decomposition:

    • Map each code change to preconditions and effects
    • Calculate effort estimates and risk factors
    • Identify dependencies and parallel opportunities
  3. Milestone Planning:

    typescript
    interface CodeMilestone {
      id: string;
      description: string;
      preconditions: string[];
      deliverables: string[];
      success_criteria: Metric[];
      estimated_hours: number;
      dependencies: string[];
    }

SPARC-Enhanced Planning Patterns

SPARC Command Integration
bash
# Execute SPARC phases for goal achievement
npx claude-flow sparc run spec-pseudocode "OAuth2 authentication system"
npx claude-flow sparc run architect "microservices communication layer"
npx claude-flow sparc tdd "payment processing feature"
npx claude-flow sparc pipeline "complete feature implementation"

# Batch processing for complex goals
npx claude-flow sparc batch spec,arch,refine "user management system"
npx claude-flow sparc concurrent tdd tasks.json
SPARC-GOAP Feature Implementation Plan
yaml
goal: implement_payment_processing_with_sparc
sparc_phases:
  specification:
    command: "npx claude-flow sparc run spec-pseudocode 'payment processing'"
    deliverables:
      - requirements_doc
      - acceptance_criteria
      - test_scenarios
    success_criteria:
      - all_payment_types_defined
      - security_requirements_clear
      - compliance_standards_identified
      
  pseudocode:
    command: "npx claude-flow sparc run pseudocode 'payment flow algorithms'"
    deliverables:
      - payment_flow_logic
      - error_handling_patterns
      - state_machine_design
    success_criteria:
      - algorithms_validated
      - edge_cases_covered
      
  architecture:
    command: "npx claude-flow sparc run architect 'payment system design'"
    deliverables:
      - system_components
      - api_contracts
      - database_schema
    success_criteria:
      - scalability_addressed
      - security_layers_defined
      
  refinement:
    command: "npx claude-flow sparc tdd 'payment feature'"
    deliverables:
      - unit_tests
      - integration_tests
      - implemented_features
    success_criteria:
      - test_coverage_80_percent
      - all_tests_passing
      
  completion:
    command: "npx claude-flow sparc run integration 'deploy payment system'"
    deliverables:
      - deployed_system
      - documentation
      - monitoring_setup
    success_criteria:
      - production_ready
      - metrics_tracked
      - team_trained

goap_milestones:
  - setup_payment_provider:
      sparc_phase: specification
      preconditions: [api_keys_configured]
      deliverables: [provider_client, test_environment]
      success_criteria: [can_create_test_charge]
      
  - implement_checkout_flow:
      sparc_phase: refinement
      preconditions: [payment_provider_ready, ui_framework_setup]
      deliverables: [checkout_component, payment_form]
      success_criteria: [form_validation_works, ui_responsive]
      
  - add_webhook_handling:
      sparc_phase: completion
      preconditions: [server_endpoints_available]
      deliverables: [webhook_endpoint, event_processor]
      success_criteria: [handles_all_event_types, idempotent_processing]
Performance Optimization Plan
yaml
goal: reduce_api_latency_50_percent
analysis:
  - profile_current_performance:
      tools: [profiler, APM, database_explain]
      metrics: [p50_latency, p99_latency, throughput]
      
optimizations:
  - database_query_optimization:
      actions: [add_indexes, optimize_joins, implement_pagination]
      expected_improvement: 30%
      
  - implement_caching_layer:
      actions: [redis_setup, cache_warming, invalidation_strategy]
      expected_improvement: 25%
      
  - code_optimization:
      actions: [algorithm_improvements, parallel_processing, batch_operations]
      expected_improvement: 15%
Testing Strategy Plan
yaml
goal: achieve_80_percent_coverage
current_coverage: 45%
test_pyramid:
  unit_tests:
    target: 60%
    focus: [business_logic, utilities, validators]
    
  integration_tests:
    target: 25%
    focus: [api_endpoints, database_operations, external_services]
    
  e2e_tests:
    target: 15%
    focus: [critical_user_journeys, payment_flow, authentication]
Show full SKILL.md (322 more words)Show less

Development Workflow Integration

1. Git Workflow Planning
bash
# Feature branch strategy
main -> feature$oauth-implementation
     -> feature$oauth-providers
     -> feature$oauth-ui
     -> feature$oauth-tests
2. Sprint Planning Integration
  • Map milestones to sprint goals
  • Estimate story points per action
  • Define acceptance criteria
  • Set up automated tracking
3. Continuous Delivery Goals
yaml
pipeline_goals:
  - automated_testing:
      target: all_commits_tested
      metrics: [test_execution_time < 10min]
      
  - deployment_automation:
      target: one_click_deploy
      environments: [dev, staging, prod]
      rollback_time: < 1min

Success Metrics Framework

Code Quality Metrics
  • Complexity: Cyclomatic complexity < 10
  • Duplication: < 3% duplicate code
  • Coverage: > 80% test coverage
  • Debt: Technical debt ratio < 5%
Performance Metrics
  • Response Time: p99 < 200ms
  • Throughput: > 1000 req$s
  • Error Rate: < 0.1%
  • Availability: > 99.9%
Delivery Metrics
  • Lead Time: < 1 day
  • Deployment Frequency: > 1$day
  • MTTR: < 1 hour
  • Change Failure Rate: < 5%

SPARC Mode-Specific Goal Planning

Available SPARC Modes for Goals
  1. Development Mode (sparc run dev)

    • Full-stack feature development
    • Component creation
    • Service implementation
  2. API Mode (sparc run api)

    • RESTful endpoint design
    • GraphQL schema development
    • API documentation generation
  3. UI Mode (sparc run ui)

    • Component library creation
    • User interface implementation
    • Responsive design patterns
  4. Test Mode (sparc run test)

    • Test suite development
    • Coverage improvement
    • E2E scenario creation
  5. Refactor Mode (sparc run refactor)

    • Code quality improvement
    • Architecture optimization
    • Technical debt reduction
SPARC Workflow Example
typescript
// Complete SPARC-GOAP workflow for a feature
async function implementFeatureWithSPARC(feature: string) {
  // Phase 1: Specification
  const spec = await executeSPARC('spec-pseudocode', feature);
  
  // Phase 2: Architecture
  const architecture = await executeSPARC('architect', feature);
  
  // Phase 3: TDD Implementation
  const implementation = await executeSPARC('tdd', feature);
  
  // Phase 4: Integration
  const integration = await executeSPARC('integration', feature);
  
  // Phase 5: Validation
  return validateGoalAchievement(spec, implementation);
}

MCP Tool Integration with SPARC

javascript
// Initialize SPARC-enhanced development swarm
mcp__claude-flow__swarm_init {
  topology: "hierarchical",
  maxAgents: 5
}

// Spawn SPARC-specific agents
mcp__claude-flow__agent_spawn {
  type: "sparc-coder",
  capabilities: ["specification", "pseudocode", "architecture", "refinement", "completion"]
}

// Spawn specialized agents
mcp__claude-flow__agent_spawn {
  type: "coder",
  capabilities: ["refactoring", "optimization"]
}

// Orchestrate development tasks
mcp__claude-flow__task_orchestrate {
  task: "implement_oauth_system",
  strategy: "adaptive",
  priority: "high"
}

// Store successful patterns
mcp__claude-flow__memory_usage {
  action: "store",
  namespace: "code-patterns",
  key: "oauth_implementation_plan",
  value: JSON.stringify(successful_plan)
}

Risk Assessment

For each code goal, evaluate:

  1. Technical Risk: Complexity, unknowns, dependencies
  2. Timeline Risk: Estimation accuracy, resource availability
  3. Quality Risk: Testing gaps, regression potential
  4. Security Risk: Vulnerability introduction, data exposure

SPARC-GOAP Synergy

How SPARC Enhances GOAP
  1. Structured Milestones: Each GOAP action maps to a SPARC phase
  2. Systematic Validation: SPARC's TDD ensures goal achievement
  3. Clear Deliverables: SPARC phases produce concrete artifacts
  4. Iterative Refinement: SPARC's refinement phase allows goal adjustment
  5. Complete Integration: SPARC's completion phase validates goal state
Goal Achievement Pattern
javascript
class SPARCGoalPlanner {
  async achieveGoal(goal) {
    // 1. SPECIFICATION: Define goal state
    const goalSpec = await this.specifyGoal(goal);
    
    // 2. PSEUDOCODE: Plan action sequence
    const actionPlan = await this.planActions(goalSpec);
    
    // 3. ARCHITECTURE: Structure solution
    const architecture = await this.designArchitecture(actionPlan);
    
    // 4. REFINEMENT: Iterate with TDD
    const implementation = await this.refineWithTDD(architecture);
    
    // 5. COMPLETION: Validate and deploy
    return await this.completeGoal(implementation, goalSpec);
  }
  
  // GOAP A* search with SPARC phases
  async findOptimalPath(currentState, goalState) {
    const actions = this.getAvailableSPARCActions();
    return this.aStarSearch(currentState, goalState, actions);
  }
}
Example: Complete Feature Implementation
bash
# 1. Initialize SPARC-GOAP planning
npx claude-flow sparc run spec-pseudocode "user authentication feature"

# 2. Execute architecture phase
npx claude-flow sparc run architect "authentication system design"

# 3. TDD implementation with goal tracking
npx claude-flow sparc tdd "authentication feature" --track-goals

# 4. Complete integration with goal validation
npx claude-flow sparc run integration "deploy authentication" --validate-goals

# 5. Verify goal achievement
npx claude-flow sparc verify "authentication feature complete"

Continuous Improvement

  • Track plan vs actual execution time
  • Measure goal achievement rates per SPARC phase
  • Collect feedback from development team
  • Update planning heuristics based on SPARC outcomes
  • Share successful SPARC patterns across projects

Remember: Every SPARC-enhanced code goal should have:

  • Clear definition of "done"
  • Measurable success criteria
  • Testable deliverables
  • Realistic time estimates
  • Identified dependencies
  • Risk mitigation strategies

© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/agent-code-goal-planner of ruvnet/ruflo.

Open the folder on GitHubat commit de590e1

Used in 3 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in ruvnet/ruflo, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Agent Code Goal Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Code Goal Planner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Code Goal Planner this skillruvnet/ruflo74k3 repos~3.6kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official37k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k34 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official37k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    37k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 34 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    37k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    794 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from ruvnet/ruflo

All 264 skills in this repo
  • Stores, searches, and retrieves successful patterns with HNSW-indexed semantic search so agents can reuse past solutions instead of relearning them.

    74k GitHub starsUsed in 2 repos~830 tokens
    Auto-check passed
  • Runs claude-flow CLI security scans for input validation, path traversal, SQL injection, XSS, hardcoded secrets and known CVEs, and writes an audit report.

    74k GitHub starsUsed in 2 repos~823 tokens
    Auto-check passed
  • Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.

    74k GitHub starsUsed in 2 repos~829 tokens
    Auto-check passed
  • Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.

    74k GitHub starsUsed in 2 repos~779 tokens
    Auto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Auto-check passed
  • Agent Coordination

    ruvnet/ruflo

    Reference for spawning, listing, monitoring and stopping agents with claude-flow commands, with agent type families, routing codes and coordination tips.

    74k GitHub starsUsed in 2 repos~519 tokens
    Auto-check passed

Categories

Questions about Agent Code Goal Planner

What does Agent Code Goal Planner do?

Agent skill for code-goal-planner - invoke with $agent-code-goal-planner. Agent Code Goal Planner is an agent skill from ruvnet/ruflo.

When should I use Agent Code Goal Planner?

Agent Code Goal Planner fits situations like: agent Workflows work in your project.

How do I install Agent Code Goal Planner in Claude Code?

Run `npx skills add ruvnet/ruflo --skill agent-code-goal-planner -a claude-code`. Or copy the skill folder (.agents/skills/agent-code-goal-planner in ruvnet/ruflo) into .claude/skills/agent-code-goal-planner in your project. Claude Code loads it when a task matches its description.

How do I install Agent Code Goal Planner in Codex?

Run `npx skills add ruvnet/ruflo --skill agent-code-goal-planner -a codex`. Or copy the skill folder (.agents/skills/agent-code-goal-planner in ruvnet/ruflo) into .agents/skills/agent-code-goal-planner in your project. Codex loads it when a task matches its description.

Can I use Agent Code Goal Planner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/ruflo --skill agent-code-goal-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-code-goal-planner, .gemini/skills/agent-code-goal-planner, .github/skills/agent-code-goal-planner and .opencode/skills/agent-code-goal-planner in your project.

What does Agent Code Goal Planner need to run?

Going by SKILL.md and its folder, Agent Code Goal Planner needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Agent Code Goal Planner access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Agent Code Goal Planner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Code Goal Planner use?

Agent Code Goal Planner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Code Goal Planner use?

About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Code Goal Planner?

Skills that share tags, products or a category with Agent Code Goal Planner: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Code Goal Planner?

ruvnet (a GitHub user) maintains it in ruvnet/ruflo, which has 74,012 GitHub stars. The repository holds 264 skills in this directory. The repository was last updated on October 7, 2026.

Source: ruvnet/ruflo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.