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/software-project-coordination.md
View on GitHub# Software Project Coordination Profile
Use this profile when the project is driven by:
- engineering planning
- specs and implementation coordination
- software project status continuity
- repo-level project organization
- multi-session software project handoff
This profile is coordination-oriented.
It is not a full autonomous coding runtime profile.
## Primary Risks
Software projects drift when:
- the implementation state and the documented state diverge
- specs and plans fall behind the actual workspace
- different sessions anchor on different assumptions
- coordination notes become a weak substitute for explicit current state
- blockers and ownership gaps stay implicit instead of visible
## What to Emphasize
In this profile, emphasize:
- verified project state continuity
- decision traceability
- spec and plan alignment
- reducing drift across sessions and tools
- clear next-step ownership at the project level
- active task visibility
- blocker visibility
- relevant files discipline
- critical context that the next session must not rediscover
## File Emphasis
- `STORAGE_ROOT/context_brief.md`
Keep mission, phase, scope, source of truth, and core workflow boundaries clear.
Prefer section keys rather than display headings when reasoning about structure:
- `mission` for project objective
- `audience_stakeholders` for team ownership and coordination surfaces
- `current_phase` for current delivery phase
- `scope` for system boundary and delivery scope
- `source_of_truth` for code/spec/plan authority
- `core_workflow` for coordination flow boundaries
Display headings may render as localized labels such as `Source of Truth` or `事实来源`.
- `STORAGE_ROOT/rolling_summary.md`
Focus on:
- `current_state` for the actual validated project state right now
- make active state explicit rather than implied
- call out the relevant files that a new session will likely need next
- call out critical context that should not be reconstructed from memory
- `active_judgments` for active coordination assumptions, tradeoffs, or decisions
- keep key decisions visible in the current snapshot rather than buried in old notes
- `risks_open_questions` for blockers, unresolved dependencies, and verification gaps
- prefer explicit blocked items over vague risk wording
- `next_step` for the next coordination move
- prefer a handoff-first active task statement, not just a generic next idea
- `STORAGE_ROOT/daily_logs/`
Record milestone implementation outcomes, validated changes, and meaningful coordination shifts.
## Common Anti-Pattern
Do not confuse software-project coordination with full coding automation.
Do not let plans or backlog notes substitute for verified current state.
RecallLoom can support software projects well at the project-state layer without claiming to replace the entire engineering execution stack.
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 |