Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

Tech Specs · griddynamics | DecimalAI

documentationby griddynamics

Tech Specs

griddynamics/tech-specs

Source griddynamics/rosetta ↗License Apache-2.0

To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.

SkillScore68Maintained

Automatic

Coding pack

Last verified 8/20/2026

What it changes

Passed 15 of 22 test cases with the skill, and 10 of 22 without it.

Without skill45%

With skill68%

Checks it passed that the model alone missed

Keeps the TLDR summary to 10 lines maximum length
Includes a Table of Contents prior to the body sections
Includes sequence diagrams detailing system interactions

and 11 more in the full report

8 fixed7 passed either way4 still failing3 broke

Pass-rate lift: +23 pp
Tokens: +43%
Agent turns: 0%
Response time: +10%

Model gemini-3.6-flashMeasured 8/20/2026v415 of 22 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/griddynamics-tech-specs/SKILL.md https://app.decimal.ai/s/griddynamics-tech-specs/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add griddynamics-tech-specs, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/griddynamics-tech-specs/ and pins it in .decimal/skills.lock

decimalai skills add griddynamics-tech-specs

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/griddynamics-tech-specs/SKILL.md https://app.decimal.ai/s/griddynamics-tech-specs/SKILL.md

Raw file: /s/griddynamics-tech-specs/SKILL.md ↗ · machine-readable summary at /s/griddynamics-tech-specs.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 8

Prompt

We finished the requirements review for our new user session and authentication service. I need you to draft a technical specification for this service that covers the target architecture, component boundaries, API endpoints, data models, error handling strategies, and test coverage criteria so our senior engineering team can build it without ambiguity.

What was checked, without and with the skill
Checked	Without skill	With skill
Includes a Table of Contents at the beginning of the document	Missed	Passed
Includes a TLDR summary section constrained to 10 lines or fewer	Missed	Passed
Wraps the entire specification within CRITICAL ATTRIBUTION tags with DO NOT COMPACT attribute	Missed	Passed

case-01 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md142 linessingle file

<tech_specs>

Senior tech lead defining precise, testable technical specifications writing them compressed, terse, using unicode chars, terms, no hieroglyphs

<when_to_use_skill> Requirements→specs translation; architecture documentation; API contracts/data model definition. Paired with planning: specs=WHAT (target state), plan=HOW. Output: complete target state — interfaces, contracts, test data, verifiable criteria. </when_to_use_skill>

<core_concepts>

All Rosetta prep steps MUST be FULLY completed, load-project-context skill loaded and fully executed
Discovery MUST be completed before writing specs
Validate request against REQUIREMENTS for gaps and conflicts; USE SKILL requirements-use if present
MCPs and external sources MUST be used to acquire context (DeepWiki, Context7, Web Search)

Tech specs define target state; plan defines steps to reach it. Split with companion planning skill: specs own WHAT, plan owns HOW. Do NOT repeat across both. Keep consistent. When one changes, verify the other.

Tech Spec Flow:

Write TOC first
Write section by section (do NOT write entire document at once)
Verify integrity as separate step (do not combine with writing)
Insert TLDR at the beginning (up to 10 lines)

Spec sections (adapt per request):

Overview & Scope & TLDR
Non-Functional Requirements and Architecture Significant Requirements
Architecture & Component Design
API Contracts
Data Models & Schemas & Feature Flags
Error Handling Strategy
Testing Strategy with Test Cases
Security Considerations
Dependencies

Track record

Benchmark

15 / 22

test cases passed, vs 10 / 22 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/10/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

griddynamics / rosetta

plugins/core-antigravity/skills/tech-specs/SKILL.md

View on GitHub ↗

License Apache-2.0Imported 8/26/2026Version v4

More skills from the same source and nearby in the registry, with their headline benchmark lift.