More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Promote Idea: From Backlog to Active Project

    1

    Turn one pending backlog idea into a real project in one exchange: concept carried verbatim, status flipped exactly once, name locked, next step named.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Promote Idea: From Backlog to Active Project

    Promote Idea: From Backlog to Active Project

    Example session with this skill installed

    Promote "Harbor Lights" from my ideas backlog — it's a song cycle idea, been sitting there for months.

    • Read your context and instructions
    • Compiled the promote idea
    • Generated the document

    PROMOTION — produced by applying the skill.

    Located: one pending entry matches "Harbor Lights" exactly. Kind on the ledger: album project. Concept on the entry, two sentences, quoted here because they are what travels: "A song cycle about a night ferry crew who see the same passenger every crossing for a year and never learn his name. Each track is a different crew member watching him."

    Name preview, shown before anything was created:

    About to promote
    Idea: Harbor Lights
    Folder: harbor-lights
    Kind: Album project

    Proceed? — confirmed by you. (Had you supplied the folder name yourself, this step would have been skipped as already signed.)

    Research folder? Asked, per protocol. The passenger is fictional and the setting invented, so your answer was no — recorded in the project notes either way, so the question is never re-litigated later. (A yes would have created the notes and sources files now, not after the first session tried to cite something from memory.)

    Executed: folder harbor-lights/ created; project notes file written with the concept pasted verbatim — diffed against the ledger text, character-identical, two sentences, unedited. Ledger entry updated in the same pass: status Pending → In Progress, folder field set to harbor-lights, so title and folder can find each other from either side.

    Integrity check: concept verbatim (2/2), status moved exactly once with both links recorded (2/2), name stable and rule-derived (2/2) — 6/6.

    Report line: Promoted "Harbor Lights" → harbor-lights/. Next step, specific to the kind: turn the concept into a track list — one track per crew member is already implied by the second sentence, so the structure work starts there, not from a blank page.

    promote-idea-from-backlog-to-active-proj.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

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

    About this skill

    Every idea backlog needs the same operation — take one pending idea and make it a project — and done by hand it quietly breaks: the concept never makes it into the project notes, or the ledger still says "pending" for work already underway, so the idea gets double-started or forgotten. This skill makes promotion a single reliable move built on three guarantees. The concept survives: it is copied word for word into the new project's notes, never summarized at transfer time, because the exact words are the contract. The status moves exactly once: Pending to In Progress as part of the same operation, with the folder recorded on the entry. The name is stable: a slug derived by fixed rules — lowercase, hyphens, diacritics stripped — previewed to you before anything is created, and never changed afterward. The conversation around it is short and ordered: locate the entry (listing pendings rather than guessing), preview the name, ask once whether the project needs a research folder from day one, then execute and report in one breath with a concrete next step for that kind of project. You get the ledger entry schema, the slug derivation table, a promotion checklist, an integrity rubric, a failure table for the ways promotion goes wrong, and a worked example. Promotion is deliberately one-way — the preview step exists because there is no unpromote.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Productivity.

    • Promotion is one-way by design: there is no unpromote, so undoing means manual cleanup (rename or remove the folder, revert the entry) — the preview step exists to make that rare.
    • It promotes one idea per conversation, deliberately. Bulk promotion would skip the per-idea preview and research question that make the operation safe.
    • It scaffolds, it does not plan: the result is a project home with the concept intact and a named next step, not a track list, outline, or roadmap.

    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 buying a skill.

    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

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Permissions

    No special permissions declared or detected

    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Because the wording is the contract. The idea was written in a specific moment with specific intent; a paraphrase at transfer time quietly replaces that intent with the mover's reading of it. Editing is welcome afterward, inside the project, where the changes are the work — not during the move.

    The preview step is the guard: you see the exact idea, derived folder, and kind before anything is created, and nothing happens without your go-ahead. If it still goes wrong, cleanup is manual — folder renamed or removed, ledger entry reverted — and the skill walks that with you rather than pretending an undo exists.

    No, by design. Each idea needs its own name preview and its own research answer; batching skips exactly the steps that keep promotion safe. It will happily walk the list with you one at a time, which in practice takes an exchange per idea.

    New in Productivity