Adopt Keelson

    2

    Establish a disciplined, issue-driven agentic operating model with automated tracking and strategic human-in-the-loop.

    Free

    12 usesSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    adopt-keelson

    Example session with this skill installed

    We need to formalize how agents work in this repo. Let's adopt the Keelson issue-driven flow.

    • Read your context and instructions
    • Compiled the adopt-keelson

    Perfect. I'll start the Keelson configuration. This will take ~8-20 rounds to map your SDLC.

    Round 1: Discovery. Can you describe your current delivery stages? From intake and triage to QA and release—what's solid, and what do you want me to tighten up?

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A Disciplined Agentic Operating Model

    The Adopt Keelson skill implements a rigorous, issue-driven workflow for your repository. It transforms your agent from a simple chatbot into a disciplined contributor that follows a structured frame → plan → implement → open-change → gate → close lifecycle. It solves the "agent chaos" problem where AI agents make uncoordinated changes, bypass repository conventions, or fail to communicate their intent.

    What it does

    This skill initiates a deliberate, multi-round configuration session (typically 8–20 rounds) to map your specific SDLC and project requirements. At a high level, it:

    • Conducts a thorough discovery phase to understand your branching models, tracker terminology (GitHub, Jira, Linear, etc.), and delivery stages.
    • Establishes the "Tactical vs. Strategic" boundary, defining exactly where the agent acts autonomously and where it must escalate for human approval.
    • Generates a repository-specific AGENTS.md substrate and a set of localized, plain-language lifecycle skills.
    • Integrates quality gates and engineering standards directly into the agent's operating instructions.

    Why developer teams use Keelson

    Unlike simple prompting, Keelson ensures your agent respects your specific "Source of Truth," documentation standards (like ADRs), and status-flow rules. The result is an agent that manages its own backlog, writes self-reviewing PRs, and never proceeds under uncertainty without asking—providing true tactical autonomy within a strategic human-in-the-loop framework.

    • High token usage during initial 8-20 round config.
    • Requires manual tracker API setup.
    • Best for repos with existing issue management.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    12 uses

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 5 months ago

    • Free with an Agensi account

    Requires

    @modelcontextprotocol/server-gitlab
    Node.js
    Remote MCP

    Permissions

    Network Access
    Listed5 months ago

    What's inside

    Frequently Asked Questions

    Adopt-keelson solves "agent chaos" by transforming your AI into a disciplined contributor that follows a strict issue-driven workflow, ensuring every code change is tracked, planned, and approved according to your specific SDLC.

    This skill is designed to work with advanced LLM-based agents capable of long-running sessions and multi-step reasoning, particularly those with repository access like GitHub Copilot, Replit Agent, or custom agents built on LangChain.

    Setup involves an 8–20 round discovery session where the agent interviews you about your project's branching models, issue trackers, and quality gates to generate your customized operating substrate.

    You receive the Keelson discovery protocol, the logic to generate your repository-specific AGENTS.md substrate, and a suite of localized lifecycle skills for framing, planning, and gating tasks.

    Yes, Keelson is designed to be tracker-agnostic; during the configuration phase, you define your specific terminology and integration points for tools like GitHub Issues, Jira, or Linear.

    Updates to the core Keelson protocol are provided via the marketplace; when a major update is released, you can simply re-run the discovery session to refresh your repository's AGENTS.md instructions.

    New in Agents & Orchestration