What problem does it solve? Long projects lose context when a chat thread ends, forcing you to re-explain goals, background, and progress in every new session. This Skill maintains a per-project long-term memory file plus timestamped thread folders (OBJECTIVE.md / OUTPUT.md) inside your repository, so any new session can resume work with full context. ## Core Features & Use Cases - Project lifecycle management: Initialize, resume, close, archive, and inventory-triage projects stored under .claude/my-projects/<slug>/ (or a custom root), with a fixed frontmatter schema tracking status, branch, PR, and issue URLs. - Thread-based work units: Split work into concrete (research/spec) and implementation threads using copyable templates, with pbcopy kickoff prompts for seamless handoff to the next session. - Retroactive adoption & import: Convert an in-progress conversation, existing PR, Issue, or branch into a fully structured project after the fact, and migrate legacy project-management formats. - Use Case: You are midway through a multi-week feature across server and client repos. Ask the agent to resume your project slug, and it reads the long-term memory and latest thread output, then proposes the next concrete steps without any re-explanation. ## Quick Start Ask the agent to start a new pj-flow project for your current task, or say "resume <slug>" to continue an existing project from its saved memory and latest thread.
