anchors

Manage requirements-driven development documents with frontmatter-driven ANCHORS.md structure.

2|1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/block/anchorsmd --skill anchors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anchors
Source: https://github.com/block/anchorsmd/tree/main/skill
Command: npx skills add https://github.com/block/anchorsmd --skill anchors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Requirements-driven development is difficult to coordinate across modules; anchors provides a framework to organize product and engineering requirements, testing strategy, and dependencies in a consistent, traceable structure.

Core Features & Use Cases

  • Lightweight frontmatter-based module markers (ANCHORS.md) that define module scope and mode.
  • Four document types: ANCHORS.md, PRODUCT.md, ENGINEERING.md, TESTING.md, DEPENDENCIES.md, with a defined truth hierarchy and backlink conventions.
  • Supports embedded and detached modes, with tooling to check traceability, cross-module references, and test coverage.

Quick Start

Install the anchors skill in your repository, then run setup to scaffold ANCHORS documents and enable traceability checks.

Frequently Asked Questions about anchors

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

FAQPage Schema
How do I manage requirements-driven documentation across multiple modules?

Requirements-driven documentation across multiple modules is managed using a standard frontmatter-driven structure, enforcing traceability and consistency. It applies to multi-module repositories with embedded or detached modes.

How do I set up ANCHORS.md files for module discovery and traceability?

To set up ANCHORS.md files for module discovery, install the skill in your repository and run setup. This scaffolds your documents and enables traceability checks across modules.

What documents are required for engineering traceability in a modular project?

Engineering traceability in a modular project requires five document types: ANCHORS.md, PRODUCT.md, ENGINEERING.md, TESTING.md, and DEPENDENCIES.md. These maintain a defined truth hierarchy and backlink conventions.

Does this requirements framework support both embedded and detached documentation modes?

Yes, this requirements framework supports both embedded and detached documentation modes. Tooling is provided to check cross-module references, traceability, and test coverage regardless of the mode chosen.

When do I need a frontmatter-driven structure for product and engineering docs?

You need a frontmatter-driven structure for product and engineering docs when coordinating development across multiple modules. It provides a lightweight module marker to define scope and organize testing strategy.

What is the best way to organize dependencies and testing strategy in a multi-module repository?

The best way to organize dependencies and testing strategy in a multi-module repository is using dedicated DEPENDENCIES.md and TESTING.md documents. This enforces documentation consistency and traceability across modules.