hmem-new-project

Generate a complete R0009-standard P-entry with YAML frontmatter from user input.

23|5|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Bumblebiber/hmem --skill hmem-new-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hmem-new-project
Source: https://github.com/Bumblebiber/hmem/tree/main/skills/hmem-new-project
Command: npx skills add https://github.com/Bumblebiber/hmem --skill hmem-new-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create standardized P-entries following the R0009 schema, reducing boilerplate and ensuring consistent project documentation from the outset.

Core Features & Use Cases

  • Scaffolds a complete P-entry from minimal input
  • Optionally scans an existing codebase to pre-fill sections
  • Supports multi-language teams and quick onboarding of new projects

Quick Start

Provide the project name, status, and stack to generate a complete P-entry.

Frequently Asked Questions about hmem-new-project

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

FAQPage Schema
What is a P-entry and why do I need standardized project documentation?

A P-entry is a standardized project documentation record following the R0009 schema. You need it to ensure consistent project governance by capturing required YAML frontmatter fields like name and description alongside structured sections.

How do I generate a complete P-entry from minimal project input?

To generate a P-entry, provide your project name, status, and stack. The system applies Step 1-2 logic to scaffold a complete R0009 record, auto-filling sections like Overview, Codebase, Usage, Context, Deployment, Bugs, Protocol, Open tasks, and Ideas.

Can I scan an existing codebase to pre-fill project documentation sections?

Yes, you can optionally scan an existing codebase to pre-fill P-entry sections. This codebase scan extracts contextual information to populate documentation fields automatically, reducing manual boilerplate when onboarding new projects or multi-language teams.

What's the best way to ensure my project documentation follows the R0009 standard?

The best way to follow the R0009 standard is using an automated P-entry generator that captures required YAML frontmatter and applies structured schema logic. This ensures all mandatory sections are properly formatted and consistently populated from project inception.

Do I need specific dependencies or environment setup to create R0009 compliant documentation?

No specific dependencies are required to create R0009 compliant documentation. You only need minimal project input including the project name and stack information to scaffold a complete P-entry with proper YAML-ready output formatting.

What limitations exist when auto-creating P-entries from a codebase scan?

The P-entry generator relies on user input and optional codebase scan results to fill sections. It cannot invent missing project context, so incomplete input yields incomplete documentation sections like Open tasks, Bugs, or Ideas that require manual review afterward.