where-we-are SKILL.md skillA

where-we-are from dataart/artisyn-implementation-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add dataart/artisyn-implementation-harness/where-we-are@v1.0.0

Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
dataart/artisyn-implementation-harness
Path
.claude/skills/where-we-are/SKILL.md
Versions recorded
4
Latest version
v1.0.0, committed Oct 1, 2026
First version recorded
Aug 17, 2026
Size
6,321 bytes
Repository stars
8
License
MIT

Delivery gap report (/where-we-are or "what's implemented vs designed?"). Compares HLD containers vs LLD docs and the codebase. Saves snapshot to docs/System Architecture (LLD)/where-we-are/.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

The developer wants to see the current delivery gap between Target Architecture (HLD) and System Architecture (LLD). Here is their input:

---

## $ARGUMENTS

---

> ⚠️ Follow every step in order. Do not skip, summarize, or improvise. If you are unsure, ask before deviating.

---

## Overview

This skill produces a **delivery gap report**: what has been designed in Target Architecture (HLD) vs what has been documented in System Architecture (LLD) vs what exists in the codebase (the NX monorepo under `apps/`).

It answers the question: _"Where are we relative to where we want to be?"_

Three dimensions are assessed per container:

| Dimension       | Source                            | Meaning                                   |
| --------------- | --------------------------------- | ----------------------------------------- |
| **Designed**    | `docs/Target Architecture (HLD)/` | Container is defined in the HLD           |
| **Documented**  | `docs/System Architecture (LLD)/` | Container has LLD docs (populated folder) |
| **Implemented** | the NX monorepo under `apps/`     | Code exists for this container            |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add dataart/artisyn-implementation-harness/where-we-are@sha256:b2c018204e5e5ca2

The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_lqyfu76d4dc66czx.svg)](https://markdownregistry.com/a/art_lqyfu76d4dc66czx)

0 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 4 versions of this file, between Aug 17, 2026 and Oct 1, 2026, about one every 15 days.

versioncommittedcommitsizeaudit
v1.0.0 latest2026-10-01 8fe47da 6,321 BA view · diff
v0.3.12026-09-16 b30e555 6,207 BA view · diff
v0.3.12026-09-15 7499382 6,182 BA view · diff
v0.3.12026-08-17 1249341 6,194 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (6321 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

dataart/artisyn-implementation-harness · 8 stars · license MIT · pushed 2026-11-09 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_lqyfu76d4dc66czx
GET https://markdownregistry.com/api/v1/resolve?ref=dataart/artisyn-implementation-harness/where-we-are
GET https://markdownregistry.com/api/v1/blob/b2c018204e5e5ca2b4bdd4248d2daa52db39840be532651355cec4442816a362

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from dataart/artisyn-implementation-harness

harness-bootstrap SKILL.md skill
dataart/artisyn-implementation-harness · .canonical-implementation-harness/SKILL.md · Install the portable AI-dev harness, rebuild its operational graph standalone, harvest project skill improvements into…
v3.3.0 · audit A · 8 stars
harness-bootstrap SKILL.md skill
dataart/artisyn-implementation-harness · .canonical-implementation-harness/patch/20260928T000002Z-era-c-approval-split-and-genericity-checkpoint-bb33b9d1-6a93-553b-9a53-ff708eb66a08/files/SKILL.md · Install the portable AI-dev harness, harvest project skill improvements into its canonical templates, package direct…
v1.3.0 · audit A · 8 stars
design SKILL.md skill
dataart/artisyn-implementation-harness · .claude/skills/design/SKILL.md · Full design lifecycle (/design {ticket}): Context Gathering → Ceremony → Frame → Research → Evaluate → Solution →…
v6.0.0 · audit A · 8 stars
dev SKILL.md skill
dataart/artisyn-implementation-harness · .claude/skills/dev/SKILL.md · Full dev lifecycle (/dev {ticket}): Context Gathering → Ceremony → Plan → Implement → Test → Document → Completion, or…
v3.1.0 · audit A · 8 stars
evolve SKILL.md skill
dataart/artisyn-implementation-harness · .claude/skills/evolve/SKILL.md · Improve harness skills, agents, workflows, and conventions from observed friction or a concrete improvement request…
git:20260915.7499382 · audit A · 8 stars
war SKILL.md skill
dataart/artisyn-implementation-harness · .claude/skills/war/SKILL.md · Well-Architected Review (/war [design|implementation] [VERSION]). Prompts design vs implementation if ambiguous, then…
v2.0.0 · audit A · 8 stars
x-ray SKILL.md skill
dataart/artisyn-implementation-harness · .claude/skills/x-ray/SKILL.md · Review a diff for correctness, project conventions and architecture alignment. Route component checks to installed…
git:20261001.8fe47da · audit A · 8 stars
design SKILL.md skill
dataart/artisyn-implementation-harness · .harness/evolve/20261102T140000Z-design-stage-tasks-first-action/candidate/SKILL.md · Full design lifecycle (/design {ticket}): Context Gathering → Ceremony → Frame → Research → Evaluate → Solution →…
v6.0.0 · audit A · 8 stars
CLAUDE.md CLAUDE.md file
dataart/artisyn-implementation-harness · CLAUDE.md
git:20261109.cbecb2c · audit A · 8 stars

Every file in dataart/artisyn-implementation-harness

Browse by kind, by grade A, or by owner.