docs-implement

Organize domain reference documents into architecture, strategy, specs, and guides.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/srnnkls/tropos --skill docs-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-implement
Source: https://github.com/srnnkls/tropos/tree/main/skills/docs-implement
Command: npx skills add https://github.com/srnnkls/tropos --skill docs-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

General-purpose domain reference documents help teams organize architecture, strategy, specs, and guides without duplicating content.

Core Features & Use Cases

  • Domain categorization for architecture, strategy, specs, and guides
  • Quick creation of architecture and strategy docs from templates
  • Cross-skill referencing and discovery of related writing tasks

Quick Start

Create a new domain reference bundle by organizing content under architecture, strategy, specs, and guides.

Frequently Asked Questions about docs-implement

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

FAQPage Schema
How do I organize domain-specific reference documents for architecture and strategy?

To organize domain-specific reference documents, you categorize them under architecture, strategy, specs, and guides. This prevents content duplication and structures your non-code artifacts for easy discovery and cross-referencing.

What is the best way to structure architecture docs and decision records?

The best way to structure architecture docs and decision records is by creating a domain reference bundle. This categorizes documents logically under architecture, strategy, specs, and guides to support structured documentation.

How do I create architecture docs, API contracts, and playbooks from scratch?

You can create architecture docs, API contracts, and playbooks by applying predefined templates for your domain reference bundle. This guides the creation of non-code artifacts quickly without duplicating existing content.

Can I use this for cross-skill referencing and discovery of related writing tasks?

Yes, you can use this for cross-skill referencing and discovery of related writing tasks. It organizes domain-specific guides and specs, enabling seamless discovery and linking across different documentation workflows.

When do I need a domain reference bundle for non-code artifacts?

You need a domain reference bundle for non-code artifacts when your team requires structured documentation for architecture, strategy, specs, and guides. It prevents content duplication and organizes domain-specific references efficiently.