New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Architectural Specification

by mohitagw15856 in mohitagw15856/pm-claude-skills

Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the…

MITAuto-check passed

Install Architectural Specification

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill architectural-specification -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills architectural-specification --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/architectural-specification .claude/skills/architectural-specification && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
architectural-specification
GitHub stars
1.4k
Token cost
~1.6k tokens
SKILL.md length
779 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the…

  • Works in 7 steps: Define scope by exclusion as well as… → State performance as a measurable with a… → Choose your specification mode… → …
  • Asked to write a specification
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: Performance,… and Output Format, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Architectural Specification is an agent skill from mohitagw15856/pm-claude-skills. Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the drawings made explicit. Use when asked to write a specification, spec a material or system, prepare an NBS-style section, or when a specification produced wildly different tender prices. Produces the scope and interface definition, the performance requirements, the product or system definition, execution and tolerance…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a specification
  • Spec a material
  • Prepare an NBS-style section
  • A specification produced wildly different tender prices

Example prompts

  • “/architectural-specification”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Define scope by exclusion as well as inclusion. Most interface defects live in the gap between two sections that each assumed the other…
  2. State performance as a measurable with a test method. 'Weathertight' is not specifiable; a pressure test to a named standard is.
  3. Choose your specification mode deliberately. Prescriptive names a product and gets what you drew. Performance describes an outcome and…
  4. If naming a product, state the equivalence rule. What 'or equal approved' means, who approves, what evidence is required, and by when.
  5. Give tolerances. Unspecified tolerance becomes whatever was achieved, and the argument happens on site with the work already built.
  6. Specify the proof. Submittals before order, samples before installation, tests during. An unproved requirement is an aspiration.
  7. Coordinate with the drawings explicitly. Where the two could conflict, say which governs.

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Architectural Specification loads about 1.6k tokens when it runs. Until then it costs about 150 tokens; SKILL.md has 779 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~150
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 779 words, ~1,631 tokens.

Download SKILL.mdSave it as .claude/skills/architectural-specification/SKILL.md (or your agent's skills folder).
name
architectural-specification
description
Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the drawings made explicit. Use when asked to write a specification, spec a material or system, prepare an NBS-style section, or when a specification produced wildly different tender prices. Produces the scope and interface definition, the performance requirements, the product or system definition, execution and tolerance requirements, and the submittals and testing schedule.

Architectural Specification Section

Wide tender prices are almost always a specification problem: three contractors read the same section and priced three different buildings. The cure is not more words. It is being precise about performance, unambiguous about who does what at the interfaces, and explicit about what must be submitted and tested — so the cheap tender and the expensive one are pricing the same thing.

What This Skill Produces

  • Scope and interfaces — what this section covers, what it does not, and who is responsible at each junction
  • Performance requirements — measurable criteria with the standard and test method named
  • Product or system definition — either a named product with an equivalence rule, or a performance description a contractor can propose against
  • Execution requirements — preparation, sequence, workmanship, and stated tolerances
  • Submittals and samples — what must be approved before order, and before installation
  • Testing and inspection — what is tested, when, to what standard, and who witnesses

Required Inputs

Ask for these if not provided:

  • The element — what is being specified, and where it occurs in the building
  • The performance it must achieve — structural, thermal, acoustic, fire, weather, durability, or appearance
  • The selection basis — whether a specific product is intended, or a performance outcome is being sought
  • The interfaces — what this element meets, and which other trades are involved
  • The procurement context — the contract form, the specification system in use, and whether equivalents are permitted

Framework: Performance, Product, Execution, Proof

  1. Define scope by exclusion as well as inclusion. Most interface defects live in the gap between two sections that each assumed the other covered the junction.
  2. State performance as a measurable with a test method. 'Weathertight' is not specifiable; a pressure test to a named standard is.
  3. Choose your specification mode deliberately. Prescriptive names a product and gets what you drew. Performance describes an outcome and transfers design risk. Mixing them accidentally is how you get an unpriceable section.
  4. If naming a product, state the equivalence rule. What 'or equal approved' means, who approves, what evidence is required, and by when.
  5. Give tolerances. Unspecified tolerance becomes whatever was achieved, and the argument happens on site with the work already built.
  6. Specify the proof. Submittals before order, samples before installation, tests during. An unproved requirement is an aspiration.
  7. Coordinate with the drawings explicitly. Where the two could conflict, say which governs.

Output Format

Show full SKILL.md (385 more words)Show less
Specification: [section] · [project] · [revision]

1. GENERAL 1.1 Scope — this section covers: [list] · Not covered by this section: [list, with the section that does] 1.2 Interfaces — [element] meets [element] at [location]; responsibility: [which section/trade] 1.3 Related sections — [refs] 1.4 Precedence — where this specification and the drawings conflict, [which governs]

2. PERFORMANCE

RequirementCriterionStandardTest method
[e.g. thermal][U-value][standard ref][method]

3. PRODUCTS

  • Mode: ☐ Prescriptive ☐ Performance ☐ Prescriptive with equivalents
  • Specified: [product, manufacturer, reference] or [performance description]
  • Equivalence: proposals accepted until [date]; must demonstrate [criteria]; approved by [who]; evidence required [what]

4. EXECUTION 4.1 Preparation — [substrate condition, tolerances required before starting] 4.2 Installation — [sequence, method, restrictions, weather limits] 4.3 Workmanship — [standard of finish, jointing, fixing] 4.4 Tolerances — [dimension: permitted deviation], each stated

5. SUBMITTALS & TESTING

ItemTypeBeforeApproved by
[shop drawings / sample / certificate / test result][order / installation / handover]

A drafting framework only. Standards, test methods, statutory requirements and product certification must be taken from current published sources and verified as applicable to your jurisdiction and contract. Fire, structural and life-safety specification requires the relevant qualified designer.

Quality Checks

  • Scope states what is excluded and which section covers it
  • Every performance requirement has a criterion, a standard, and a test method
  • The specification mode is deliberate and consistent within the section
  • The equivalence rule states the evidence, the approver, and the deadline
  • Tolerances are given for every dimension that matters
  • Submittals distinguish what is needed before order from before installation
  • Precedence between specification and drawings is stated

Anti-Patterns

  • 'Or equal approved' with no rule. Guarantees a dispute at tender and again at submittal.
  • Unmeasurable performance. 'Robust', 'high quality', 'to a good standard' — none of these can be priced or enforced.
  • Silence on tolerance. The tolerance becomes whatever was built.
  • Mixing prescriptive and performance by accident. Contractors price the risk, and price it high.
  • No interface allocation. The junction is everyone's responsibility, so it is nobody's.
  • Copying a section from another project. Carries the last building's assumptions into this one.
  • Specifying without submittals. No proof required means no compliance achieved.

Example Trigger Phrases

  • "Write a specification section for the external cladding"
  • "Our tender prices came back wildly different — is it the spec?"
  • "How do I write a performance specification for windows?"
  • "What should 'or equal approved' actually say?"
  • "Write the execution and tolerance clauses for this finish"

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/architectural-specification of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Architectural Specification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Architectural Specification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Architectural Specification this skillmohitagw15856/pm-claude-skills1.4k—~1.6kAutomated safety check: PassMIT
Pricingsickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: PassMIT
Architecture Patternswshobson/agents40k—~2kAutomated safety check: PassMIT
Pricing Strategyphuryn/pm-skills27k—~913Automated safety check: PassMIT
Android Clean Architectureaffaan-m/ECC276k4 repos~2.2kAutomated safety check: PassMIT
Architecture Patternsdavila7/claude-code-templates33k4 repos~483Automated safety check: PassMIT

Similar skills

  • Pricing

    sickn33/agentic-awesome-skills

    When the user wants help with pricing decisions, packaging, or monetization strategy.

    47k GitHub starsUsed in 1 repo~1.9k tokens
    Sales & SupportAuto-check passed

  • Architecture Patterns

    wshobson/agents

    Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

    40k GitHub stars~2k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Pricing Strategy

    phuryn/pm-skills

    Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity.

    27k GitHub stars~913 tokensUpdated today
    Sales & SupportAuto-check passed

  • Android Clean Architecture

    affaan-m/ECC

    Applies Clean Architecture to Android and Kotlin Multiplatform projects: module layout, dependency rules, UseCases, Repositories and data layer patterns.

    276k GitHub starsUsed in 4 repos~2.2k tokens
    DevelopmentAuto-check passed

  • Architecture Patterns

    davila7/claude-code-templates

    Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

    33k GitHub starsUsed in 4 repos~483 tokens
    DevelopmentAuto-check passed

  • Architecture Docs Writer

    prisma/orm

    Official

    Guides writing and rewriting architecture subsystem docs, ADRs and reference pages so they make sense to a developer with no prior project context.

    48k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo

  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Architectural Specification

What does Architectural Specification do?

Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the…. Architectural Specification is an agent skill from mohitagw15856/pm-claude-skills. Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the drawings made explicit.

When should I use Architectural Specification?

Architectural Specification fits situations like: asked to write a specification; spec a material; prepare an NBS-style section; A specification produced wildly different tender prices.

How do I install Architectural Specification in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill architectural-specification -a claude-code`. Or copy the skill folder (skills/architectural-specification in mohitagw15856/pm-claude-skills) into .claude/skills/architectural-specification in your project. Claude Code loads it when a task matches its description.

How do I install Architectural Specification in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill architectural-specification -a codex`. Or copy the skill folder (skills/architectural-specification in mohitagw15856/pm-claude-skills) into .agents/skills/architectural-specification in your project. Codex loads it when a task matches its description.

Can I use Architectural Specification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill architectural-specification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/architectural-specification, .gemini/skills/architectural-specification, .github/skills/architectural-specification and .opencode/skills/architectural-specification in your project.

What does Architectural Specification need to run?

SKILL.md names no scripts, command-line tools or credentials: Architectural Specification is instructions for the agent only.

Does Architectural Specification access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Architectural Specification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Architectural Specification use?

Architectural Specification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Architectural Specification use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Architectural Specification?

Skills that share tags, products or a category with Architectural Specification: Pricing (sickn33/agentic-awesome-skills, 47k stars), Architecture Patterns (wshobson/agents, 40k stars), Pricing Strategy (phuryn/pm-skills, 27k stars) and Android Clean Architecture (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Architectural Specification?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.