build-manifest

Generate BUILD-GUIDE.json and BUILD-GUIDE.md from Airtable plugin commands.

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/vanman2024/planning-marketplace --skill build-manifest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-manifest
Source: https://github.com/vanman2024/planning-marketplace/tree/main/plugins/planning/_archive/skills/build-manifest
Command: npx skills add https://github.com/vanman2024/planning-marketplace --skill build-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyairtable, and includes scripts (resource) components.

What problem does it solve?

This skill streamlines the generation of BUILD-GUIDE manifests by aggregating plugin data and commands from Airtable into structured, layered execution plans.

Core Features & Use Cases

  • Automatically discovers plugins that match the detected tech stack and maps them to commands
  • Organizes commands into four execution layers: Infrastructure Foundation, Tech Stack Initialization, Feature Implementation, and Quality & Deployment
  • Detects gaps where technologies are mentioned but no plugin exists and surfaces actionable recommendations
  • Emits both machine-readable BUILD-GUIDE.json and human-friendly BUILD-GUIDE.md for project planning

Quick Start

Run the manifest generator to produce BUILD-GUIDE.json and BUILD-GUIDE.md from Airtable plugin indexes using architecture docs.

Frequently Asked Questions about build-manifest

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

FAQPage Schema
How do I generate a BUILD-GUIDE manifest from Airtable plugin data?

To generate a BUILD-GUIDE manifest, query Airtable for plugin commands using an API token and map detected technologies into layered execution plans. The process outputs both machine-readable JSON and human-friendly Markdown files for project planning.

What is a layered execution plan for architecture-driven projects?

A layered execution plan organizes commands into four execution layers: Infrastructure Foundation, Tech Stack Initialization, Feature Implementation, and Quality & Deployment. It maps detected technologies to plugins and flags gaps where no plugin exists.

Do I need an Airtable API token to map detected technologies to plugins?

Yes, you need an Airtable API token set as AIRTABLE_TOKEN and the specific base ID appHbSB7WhT1TxEQb. You also need architecture documentation located in the docs/architecture path to map technologies to plugins.

Can I output both JSON and Markdown files for build planning?

Yes, the manifest generator emits both machine-readable BUILD-GUIDE.json and human-friendly BUILD-GUIDE.md. These outputs aggregate Airtable plugin data into structured, layered execution plans for architecture-driven project planning.

What happens if a technology is mentioned in the architecture docs but no plugin exists?

When no plugin exists for a technology mentioned in the architecture documentation, the system detects the gap and surfaces actionable recommendations. This ensures missing plugins are flagged within the generated BUILD-GUIDE artifacts.

Why does my build manifest generator not find any plugins for my tech stack?

If the build manifest generator finds no plugins, verify your AIRTABLE_TOKEN is valid and the base ID appHbSB7WhT1TxEQb is correct. Ensure your architecture documentation path docs/architecture accurately lists the detected technologies.