Frappucc1no/recall-loom / skills/recallloom
recallloom
FlaggedUse when a task involves continuing a project, restoring project context, maintaining file-based project memory, updating current-state summaries, or recording meaningful progress across sessions. Works best for long-horizon, file-based projects and supports research writing, product document collaboration, software project coordination, and broader cross-functional project continuity.
profiles/product-doc-collaboration.md
View on GitHub# Product Document Collaboration Profile
Use this profile when the project is driven by:
- PRDs
- RFCs
- strategy docs
- scope discussions
- stakeholder-aligned product writing
## Primary Risks
Product-document projects drift when:
- scope changes are discussed but not reflected in the current state
- stakeholder concerns are remembered vaguely
- old priorities linger after a new decision
- milestone document progress gets mixed with loose brainstorming
- review comments and rejected options get mistaken for settled direction
## What to Emphasize
In this profile, emphasize:
- decision traceability
- scope drift control
- stakeholder context
- source-of-truth clarity
- next-step clarity
- phase-aware document progress
## File Emphasis
- `STORAGE_ROOT/context_brief.md`
Keep the project mission, audience, phase, scope, source of truth, core workflow, and decision boundaries explicit.
Prefer section keys rather than display headings when reasoning about structure:
- `mission` for document purpose
- `audience_stakeholders` for readers and stakeholders
- `current_phase` for the active document phase
- `scope` for product surface and decision scope
- `source_of_truth` for the current authoritative document or decision surface
- `core_workflow` for how discussion, review, and document updates should move
- `boundaries` for decision constraints and non-goals
Display headings may render as localized labels such as `Audience / Stakeholders` or `受众与相关方`.
- `STORAGE_ROOT/rolling_summary.md`
Focus on:
- `current_state` for the current document and product state
- `active_judgments` for stable product direction or tradeoff decisions
- `risks_open_questions` for unresolved concerns, review blockers, or approval gaps
- `next_step` for the next recommended document, review, or alignment move
- `STORAGE_ROOT/daily_logs/`
Record milestone decisions, completed sections, and feedback turns that materially changed the working model.
## Common Anti-Pattern
Do not treat every discussion point as a durable decision.
Do not mix brainstorm threads, rejected options, or loose comments into current truth.
Only write stable product direction into maintained memory once it materially changes the working model.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |