cypher

Draft PRDs, user stories, and acceptance criteria for VIA sprints.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/drusifer/via --skill cypher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cypher
Source: https://github.com/drusifer/via/tree/main/agents/cypher.docs
Command: npx skills add https://github.com/drusifer/via --skill cypher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bob-protocol, chat, make.

What problem does it solve?

Cypher PM helps product teams define and maintain VIA's product vision, PRDs, roadmaps, and acceptance criteria across sprints.

Core Features & Use Cases

  • Vision governance: define, align, and update VIA's product strategy with stakeholders.
  • Artifact production: draft PRDs, USER_STORIES, roadmaps, and success metrics.
  • Sprint planning and gating: map backlog items to acceptance criteria and review points for handoffs.

Quick Start

Coordinate a sprint by drafting a PRD and a set of user stories with acceptance criteria, then share the plan with the team via chat and hand off to the next engineering cycle.

Frequently Asked Questions about cypher

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

FAQPage Schema
How do I draft PRDs and user stories with acceptance criteria for sprint planning?

Drafting PRDs and user stories involves producing artifacts like USER_STORIES.md and roadmap updates, mapping backlog items to testable acceptance criteria, and coordinating handoffs through team chat for the next engineering cycle.

What is the best way to maintain a product vision and roadmap across sprints?

Maintaining product vision and roadmaps across sprints requires governing the strategy with stakeholders, producing roadmap artifacts, and ensuring requirements remain testable and traceable throughout sprint cycles.

Can I use chat and Bob to coordinate sprint work and backlog handoffs?

Yes, you can use chat and the Bob protocol to coordinate sprint work. The process maps backlog items to acceptance criteria and review points, facilitating handoffs through Bob, chat, and related artifacts.

Does generating acceptance criteria require testable and traceable requirements?

Yes, generating acceptance criteria requires testable and traceable requirements. This ensures that PRD updates, user stories, and roadmap items can be verified and properly gated for sprint handoffs.

Why map backlog items to acceptance criteria before engineering handoffs?

Mapping backlog items to acceptance criteria before handoffs ensures sprint work meets testable, traceable requirements and clear review points, aligning engineering execution with the defined product vision and PRD.