agentsclimarketplace
Sign in

Backlog brief

Skill brian8a1/senso-agent-skills/skills/backlog-brief

Brief a product manager, designer, or engineer who is beginning work on one Senso Backlog item. Use when the user names a SEN reference, Opportunity, Solution, issue, branch, design task, or current work item and needs the relevant problem, Signals, Decision, Living Document, constraints, contradictions, and success expectation without an invented implementation workflow.From its SKILL.md

Install
npx -y skills add brian8a1/senso-agent-skills --skill backlog-brief

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 379 tokens by cl100k_base, as published. Nobody here has run it

Brief one Backlog item

Bring the product context for the current work into the user's existing design or engineering workflow. Stay read-only unless the user explicitly asks the agent to take ownership.

Procedure

  1. Resolve a supplied SEN-{n}, UUID, title, issue, or branch reference with senso_lookup. If no item is supplied, query mode: work_queue and ask the user to select rather than silently taking work.
  2. Read the Solution, parent Opportunity, relevant Living Document, recent Decisions/comments, and cited Signals needed to understand conflicts or constraints.
  3. Adapt the brief to the work already in front of the user:
    • Product manager: evidence, alternatives, decision gaps, ownership, and state.
    • Designer: affected user/context, observed behavior, contradictions, constraints, and unresolved product questions.
    • Engineer: expected observable behavior, product rationale, constraints, prior decisions, risks, and questions requiring product authority.
  4. If the user explicitly asks to take an Active item, use senso_decide mode=update_solution to assign it to the current agent and post one concise start comment.
  5. Hand control back to the user's normal tools and repository/design conventions. Do not manufacture Senso-specific working files.

Guardrails

  • Never take Draft, In Review, Done, Canceled, snoozed, or already-owned work without explicit authorization.
  • Read the Living Document before opening many raw Signals; follow snippet:// citations selectively.
  • Do not create spec.md, plan.md, task lists, branches, or code merely because the brief was requested.
  • Label missing information as a question, not a requirement.

Result

Return a role-adapted brief with Senso references, known decisions, contradictions, missing answers, current Backlog state, and ownership.

What ships with it: 1 file

486 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,764. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.