Proposal to Bundle generator-parse into yo Core for Micro-Scaffolding

[mshima]

Summary

I propose transferring https://github.com/mshima/generator-parse to the yeoman organization and bundling it directly into yo. The goal is to provide a minimalist, documentation-driven way to handle small features and file-level scaffolds that don't justify the overhead of a full generator.

Why this is needed: The "Micro-Feature" Gap

While Yeoman is excellent for bootstrapping entire projects, it is often too heavy for incremental development.

• The Problem: If a developer wants to share a template for a single "Standard React Component" or a "GitHub Action Workflow," they currently have to create a full NPM package.
• The Solution: Using generator-parse, a developer can simply link to a .md file. It turns yo from a "Project Bootstrapper" into a "Daily Productivity Utility."

Key Advantages for Small Features

1. Lightweight Maintenance: Instead of maintaining a complex folder structure (templates/, index.js, etc.), a small feature can live in a single Markdown file.
2. Snippet-to-File Workflow: It bridges the gap between a static snippet and a full generator. It’s perfect for adding individual files (like a .eslintrc or a specific API route) into an existing project.
3. Low Friction for Teams: Teams can host a library of "Feature Templates" in a simple documentation folder or a GitHub Wiki. Users just run yo parse to inject that feature into their local workspace.
4. Instant Tooling: By bundling this into yo, we eliminate the "empty engine" problem. yo becomes a tool that can execute any remote logic documented in Markdown immediately.

Proposed Workflow

Add a parse command to yo. That will execute parse generator directly.

[mshima]

cc @UlisesGascon @JoshuaKGoldberg