add-objective

Upserts repository objectives to Supabase and distributes updated OBJECTIVES.md files globally.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill add-objective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-objective
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/add-objective
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill add-objective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishing and maintaining consistent core objectives across multiple repositories and branches to prevent misalignment and duplicated effort.

Core Features & Use Cases

  • Upsert to a central rule ledger in Supabase to record repository objectives.
  • Distribute updated OBJECTIVES.md files across all related repos to ensure global alignment.
  • Handle creation and updates from user requests, supporting tracking of strategic goals and fixing misalignment.

Quick Start

Provide the objective for the target repository and trigger the distribution workflow to apply and sync it globally.

Frequently Asked Questions about add-objective

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

FAQPage Schema
How do I sync repository objectives across multiple branches and teams?

To sync repository objectives, you upsert the goal into a central Supabase rule ledger and trigger a distribution script that generates local OBJECTIVES.md files across all related repos to ensure global alignment.

What is the best way to track core feature objectives for a repository?

The best way to track core feature objectives is by upserting them into a central Supabase rule ledger, which records the goals and allows you to align new features with business targets and track changes globally.

How does distributing an OBJECTIVES.md file prevent misalignment between repos?

Distributing an OBJECTIVES.md file prevents misalignment by pushing the upserted objective from the central Supabase ledger to all related repositories, establishing a single source of truth and eliminating duplicated effort.

Do I need a Supabase database to manage and sync repo objectives?

Yes, you need a Supabase database because the Skill upserts records into a central rule_ledger.objectives table in Supabase, which acts as the authoritative source before the distribution script generates local files.

Can I update an existing objective for a specific branch without breaking global sync?

Yes, you can update an existing objective without breaking global sync because the process upserts the changes to the central Supabase ledger and automatically runs the distribution script to sync the updated OBJECTIVES.md files across all related repos.