guide

Reads project memory and doc state to determine the current phase and suggest the next Scrum documentation action.

Updated May 24, 2026
One-click install
npx skills add https://github.com/pirras-torres/pirras-marketplace --skill guide-pirras-torres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: guide
Source: https://github.com/pirras-torres/pirras-marketplace/tree/main/plugins/pi-dev/skills/guide
Command: npx skills add https://github.com/pirras-torres/pirras-marketplace --skill guide-pirras-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working on a software project incrementally with Scrum documentation, it is easy to lose track of which phase you are in and which document to produce next. This Skill reads your project memory and existing docs, determines the current phase, and tells you the exact next action. ## Core Features & Use Cases - Phase Detection: Scans the docs folder and project_memory.md to classify the project as Foundation, Architecture, or Slice Cycle, flagging discrepancies between memory and actual files. - Next-Action Orchestration: Suggests the concrete next skill to run (e.g., prd, backlog, sprint-planning) and invokes it, enforcing rules like no sprint planning without a Definition of Ready. - Persistent Memory Updates: Maintains project_memory.md with phase, active slice, sprint state, blockers, and last action after every session. - Use Case: At the start of a work session, run the guide to learn that your Foundation docs are done but the backend architecture is missing, then immediately generate it. ## Quick Start Ask the assistant to run the guide skill to check my project status and tell me what to do next.

Frequently Asked Questions about guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I know which Scrum document to write next in my project?▼

Run the guide skill at the start of each session. It reads project_memory.md and scans your docs folder to determine whether you are in the Foundation, Architecture, or Slice Cycle phase, then suggests the concrete next document to create.

How does the guide skill track project progress across sessions?▼

It maintains a project_memory.md file in the project root recording the current phase, active slice, sprint state, blockers, and last action. The file is read at session start and updated after every completed action.

What happens if project memory and actual docs disagree?▼

The guide cross-references memory against files found in the docs folder. If memory says Foundation is complete but the PRD is missing, it flags the discrepancy and corrects the memory before suggesting next steps.

Can I start sprint planning before the backlog exists?▼

No. The guide enforces dependency rules: sprint planning requires a backlog and a Definition of Ready, backlog requires a completed slice discovery, and only one slice may be active at a time.

What folder structure does the guide skill expect?▼

It searches for a docs folder containing numbered subfolders such as 01_product, 02_business, 03_design, 04_tech, 05_scrum, and 06_decisions. If multiple docs folders exist, it asks which one to use; if none exists, it creates docs/.