skills.rest
memorysaver
memorysaverCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sibyl-originate

Interview users about product vision and objectives to draft structured README documents.

Updated Aug 27, 2026
Search Tags:#project planning#product definition#co-creation#README generation#vision articulation
One-click install
npx skills add https://github.com/memorysaver/SIBYL --skill sibyl-originate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sibyl-originate
Source: https://github.com/memorysaver/SIBYL/tree/main/apps/harness/skills/sibyl-originate
Command: npx skills add https://github.com/memorysaver/SIBYL --skill sibyl-originate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps to focus and articulate half-formed project ideas into clear, actionable READMEs, ensuring a focused product definition for subsequent steps.

Core Features & Use Cases

  • Guided Interview Process: Engages users in a conversational interview to elicit the product, problem, and vision.
  • README Drafting: Proactively drafts a README with sections for problem and vision based on user input.
  • Refinement & Commitment: Collaboratively refines the README and commits it upon user approval.
  • Use Case: For a project with an unclear scope, use this Skill to generate a focused README that sets the direction for the envisioning phase.

Quick Start

Use the sibyl-originate skill to create a README for your project by providing a project name and initial ideas.

Frequently Asked Questions about sibyl-originate

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

FAQPage Schema
How do I create a project README from a vague product idea?▼

To create a project README from a vague idea, this Skill engages you in a guided interview to articulate your product vision and problem. It then proactively drafts a structured README document ready for development planning.

What is the best way to document product definition for a new project?▼

The best way to document product definition is through an interactive interview process that captures your vision and objectives. This approach collaboratively refines the README sections to ensure a focused scope before committing.

How does a guided interview process help with project planning?▼

A guided interview process helps with project planning by extracting your half-formed product ideas and transforming them into structured README sections. This ensures your vision articulation is clear and actionable for subsequent steps.

Can I collaboratively refine a generated README before committing it?▼

Yes, you can collaboratively refine the generated README before committing. The Skill allows you to adjust the drafted problem and vision sections, committing the document to git only upon your final approval.

Do I need a specific environment to generate README documents for project envisioning?▼

You need an environment that supports user interaction for content refinement and git commands for committing the final README. No external dependencies are required, making it accessible for early-stage project envisioning.

Related Skills

Explore More Product & Management Skills→
majedsiefalnasrmajedsiefalnasr

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
boringdataboringdata
2

Persona Extraction Skill

Extract audience persona profiles from content and save them to rules/personas/.

Community
Advanced
zephyrwang6zephyrwang6
14

long-term-plan

Break long-term goals into milestones, tasks, and schedules.

Community
Advanced
csuzngjhcsuzngjh
1

init-strategy

Guide a structured interview to define project vision and write docs/STRATEGY.md.

Community
Intermediate