AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Backlog Recall

skill-loremaster-ai-loremaster-backlog-recall · by loremaster-ai

>

↗ Repository
— No reviews yet
0 installs
15 views
0.0% view→install

Install

$ agentstack add skill-loremaster-ai-loremaster-backlog-recall

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-loremaster-ai-loremaster-backlog-recall)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 22d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Backlog Recall? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Backlog re-kickoff — absorb a large-scale plan change

When the plan changes substantially in Slack, an already-started backlog item's decision/progress are based on the old plan — discard them and re-lay them against the new plan.

0. Input

  • Argument = the issue key (-N, e.g. PROJ-32 — a.k.a. ticket). If missing, ask the user.

1. Get the latest plan (local lore vault)

  • vault = the project's lore-vault clone (e.g. a sibling checkout ../-lore-vault/; raw/ and wiki/concepts/ sit directly at the vault root). Freshen: git -C ../-lore-vault pull --ff-only -q (proceed even if it fails).
  • Do not copy into repo docs/ — the re-kickoff (backlog-kickoff in Step 3) reads the PRD, decisions, and concepts directly from the lore vault raw/ and wiki/concepts/. (The plan's source = the lore vault.)

2. Discard this item's old artifacts

  • Delete docs/decisions/decision_-N.md + docs/progress/progress_-N.md (based on the old PRD — void).

3. Re-kickoff — run backlog-kickoff

  • Run the backlog-kickoff skill with ` → regenerates the empty decision skeleton + progress against the new PRD/wiki. (If the Jira status is already In Progress`, leave it.)

Rules

  • Do not git push. Leave the docs deletions in the working tree (backlog-complete commits and pushes after development).
  • Do not edit the PRD itself here — this skill only pulls the plan already changed in Slack down locally and re-kicks off.
  • Read only this project's docs and this project's lore vault.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills