intake-normalizer

Convert scattered notes, logs, ideas, and issues into structured Intake Markdown files.

18|9|Updated Apr 20, 2025
One-click install
npx skills add https://github.com/PHMbench/PHM-Vibench --skill intake-normalizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intake-normalizer
Source: https://github.com/PHMbench/PHM-Vibench/tree/main/.codex/skills/intake-normalizer
Command: npx skills add https://github.com/PHMbench/PHM-Vibench --skill intake-normalizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts scattered inputs such as notes, logs, ideas, and issues into a single, structured Intake Markdown file saved under the current day directory as <MM_DD>/codex/intake/intake_<topic>.md. This ensures consistent formatting and easy archival.

Core Features & Use Cases

  • Enforces a daily directory structure and a fixed Intake Markdown template.
  • Normalizes raw inputs into a reusable intake_<topic>.md format with standard fields (Goal, Scope, Tasks, Priority, Due, Owner, Background, Details, Acceptance/DoD, Notes, Evidence).
  • Ideal for personal productivity and team collaboration when collecting diverse inputs and turning them into shareable, well-structured intake documents.

Quick Start

Provide the current date and a topic, paste the raw intake materials, and the system will generate <MM_DD>/codex/intake/intake_<topic>.md using the required template.

Frequently Asked Questions about intake-normalizer

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

FAQPage Schema
How do I convert scattered notes and logs into a structured intake markdown file?

To convert scattered notes into a structured intake markdown file, you provide the current date, a topic, and your raw materials. The system normalizes these inputs into a standardized markdown template with fields like Goal, Scope, and Tasks for consistent daily archival.

What is the best way to normalize daily raw inputs into a consistent documentation template?

Normalizing daily raw inputs into a consistent documentation template involves applying a fixed field structure to diverse materials like logs and ideas. This ensures your intake topics always follow a predictable format containing sections like Background, Details, and Acceptance/DoD.

Does the intake normalizer enforce a specific daily directory structure for output files?

Yes, the intake normalizer enforces a strict daily directory structure. It automatically generates your normalized markdown file under a date-based directory named <MM_DD> and saves it specifically as codex/intake/intake_<topic>.md for easy retrieval.

Can I use this markdown normalization for both personal productivity and team collaboration workflows?

You can use this markdown normalization for both personal productivity and team collaboration workflows. It is designed to collect diverse inputs from either context and turn them into shareable, well-structured intake documents using a standardized template.

What standard fields are included when structuring raw inputs into an intake markdown format?

When structuring raw inputs into an intake markdown format, the template includes standard fields such as Goal, Scope, Tasks, Priority, Due, Owner, Background, Details, Acceptance/DoD, Notes, and Evidence to ensure comprehensive documentation.