Name: documents
Author: ydnikolaev

Imported from ydnikolaev/antigravity-factory (src/_meta/schema/documents/AGENTS.md). Install upstream with npx skills add ydnikolaev/antigravity-factory --skill documents. Copyright stays with the author.

Document Schema

Entry point for AI agents creating document templates.

Quick Start

Copy existing template as base (e.g., _tech-spec.md)
Update frontmatter: owner, upstream, downstream
Define sections appropriate for doc type
Run make doc-validate to check

Template Structure

---
status: Draft
owner: @skill-name
lifecycle: per-feature
work_unit: {WORK_UNIT}

upstream:
  - doc_type: context-map
    owner: @bmad-architect
downstream:
  - skill: @backend-go-expert

created: {DATE}
updated: {DATE}
---

# Doc Type: {WORK_UNIT}

## Overview
<!-- Brief description -->

## Details
<!-- Main content -->

## Checklist
- [ ] Item 1

Key Files

File	Purpose
`document-schema.yaml`	Core schema
`enums/enums.yaml`	References shared enums
`../../shared/factory.yaml`	Shared: phases, categories
`../../shared/runtime.yaml`	Shared: statuses, lifecycles, triggers
`examples/`	Example templates

Frontmatter Fields

Field	Required	Description
`status`	✅	Draft, In Progress, Review, Approved, Archived
`owner`	✅	@skill-name that creates this doc
`lifecycle`	✅	per-feature, per-work-unit, living
`work_unit`	✅	Work unit ID
`upstream`	❌	Docs this depends on
`downstream`	❌	Skills/docs that consume this
`created`	✅	Creation date
`updated`	✅	Last update date

Related Files

doc-types.yaml — Auto-generated doc type registry
DOCUMENT_FLOW.md — Document lifecycle

Install documents and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "ydnikolaev-antigravity-factory-documents", "kind": "skill", "name": "documents", "description": "1. Copy existing template as base (e.g., `_tech-spec.md`) 2. Update frontmatter: owner, upstream, downstream 3. Define sections appropriate for doc type 4. Run `make doc-validate` to check", "publisher": "ydnikolaev", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "1. Copy existing template as base (e.g., `_tech-spec.md`) 2. Update frontmatter: owner, upstream, downstream 3. Define sections appropriate for doc type 4. Run `make doc-validate` to check" ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/ydnikolaev/antigravity-factory", "path": "src/_meta/schema/documents/AGENTS.md", "ref": "00d55deb4f937385eecb8d4556fdd3c5cf8e36a1", "url": "https://github.com/ydnikolaev/antigravity-factory/blob/00d55deb4f937385eecb8d4556fdd3c5cf8e36a1/src/_meta/schema/documents/AGENTS.md", "key": "ydnikolaev/antigravity-factory/src/_meta/schema/documents/AGENTS.md" } }, "instructions": "# Document Schema\n\n> Entry point for AI agents creating document templates.\n\n## Quick Start\n\n1. Copy existing template as base (e.g., `_tech-spec.md`)\n2. Update frontmatter: owner, upstream, downstream\n3. Define sections appropriate for doc type\n4. Run `make doc-validate` to check\n\n## Template Structure\n\n```markdown\n---\nstatus: Draft\nowner: @skill-name\nlifecycle: per-feature\nwork_unit: {WORK_UNIT}\n\nupstream:\n - doc_type: context-map\n owner: @bmad-architect\ndownstream:\n - skill: @backend-go-expert\n\ncreated: {DATE}\nupdated: {DATE}\n---\n\n# Doc Type: {WORK_UNIT}\n\n## Overview\n<!-- Brief descrip", "cost": { "context_tokens": 409 } }

documents

About

Document Schema

Quick Start

Template Structure

Key Files

Frontmatter Fields

Related Files

Install documents and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews