agentsclimarketplace
Sign in

Ontology technical plan writer

Skill Mokee04/ontology_research/ontology-technical-plan-writer

Draft or refine a technical planning document template for an ontology project. Use when the user wants a technical proposal, planning brief, or reusable template that connects scope, competency questions, standards reuse, modeling approach, validation, governance, and execution phases without drifting into a business-only pitch.From its SKILL.md

Install
npx -y skills add Mokee04/ontology_research --skill ontology-technical-plan-writer

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 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

1.6 KB, 268 tokens by cl100k_base, as published. Nobody here has run it

Ontology Technical Plan Writer

Read:

  • ../refs/Total Guide.md
  • ../shared/references/templates.md
  • ./references/technical-planning-template.md

Use this skill when the user wants a technical ontology planning document or a reusable template for one.

Tasks

  1. Decide whether the user needs a blank template, a lightly customized template, or a first populated draft.
  2. Reuse existing planning artifacts when they exist, especially scope, competency questions, risks, and required standards.
  3. Structure the document around technical decision-making, not business marketing language.
  4. Prefer tables for scope, CQ summary, data feasibility, risks, approval gates, and open questions.
  5. Keep planned work, completed evidence, and open assumptions clearly separated.
  6. Mark approval gates, validation checkpoints, and unresolved questions explicitly.

Outputs

Write or refine one of:

  • ../exe/<run-id>/planning/technical-plan.md
  • a standalone markdown planning document when no run folder exists yet

Guardrails

  • do not present unverified research as settled fact
  • do not collapse scope, modeling, and validation into one vague summary
  • do not omit reuse-first or CQ-first rationale
  • do not write a budget or sales deck unless the user asks for it

What ships with it: 1 file

3.0 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,851. 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.