agentsclimarketplace
Sign in

Documentation architecture

Skill planifest/planifest-framework/planifest-framework/external-skills/documentation-architecture

Author architecture documentation that explains boundaries, dependencies, and operational constraints for engineering decision-making. Use when architecture docs are primary deliverables or must be updated after structural changes; do not use for implementing production feature logic.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill documentation-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, 402 tokens by cl100k_base, as published. Nobody here has run it

Documentation Architecture

Overview

Use this skill to produce architecture documents that improve shared understanding and reduce design/review ambiguity.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Review checklist:
    • references/architecture-doc-review-checklist.md

Templates And Assets

  • Architecture document template:
    • assets/architecture-doc-template.md
  • Risk register template:
    • assets/architecture-risk-register-template.csv

Inputs To Gather

  • System boundary and component inventory.
  • Dependency relationships and data/control flows.
  • Key constraints (security, reliability, compliance, cost).
  • Existing ADRs and known architecture risks.

Deliverables

  • Architecture narrative and structural views.
  • Boundary and dependency explanations.
  • Constraint and tradeoff summary.
  • Open risks/assumptions and follow-up items.

Quick Structure Template

  1. Context and goals.
  2. System boundaries and major components.
  3. Interaction/data flow and trust boundaries.
  4. Operational constraints and failure behavior.
  5. Known risks and decision links.

Quality Standard

  • Audience can answer "what talks to what" and "why" quickly.
  • Boundaries and ownership are explicit.
  • Constraints and tradeoffs are concrete.
  • Document links to decisions and unresolved risks.

Workflow

  1. Identify target audience and key questions.
  2. Build boundary/dependency narrative and diagrams using assets/architecture-doc-template.md.
  3. Capture constraints and tradeoffs, and track open risks in assets/architecture-risk-register-template.csv.
  4. Validate against current implementation and decisions with references/architecture-doc-review-checklist.md.
  5. Publish with ownership and update cadence.

Failure Conditions

  • Stop when architecture boundaries remain ambiguous.
  • Stop when documentation omits critical operational constraints.
  • Escalate when docs conflict with accepted architecture decisions.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,645. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.