ferueda/harness · Archived

shape-requirements

Clarify material requirements that block useful progress, or interview a user to develop a brief. Not for routine implementation choices or ordinary document edits.

First seen Jun 26, 2026

Installation

$ npx skills add ferueda/harness --skill shape-requirements

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from ferueda/harness · top by installs.

npx skills add ferueda/harness

Browse all from ferueda/harness

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,491 B
  • docs SUMMARY.md 190 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 8 installs

SKILL.md

Shape Requirements

Resolve missing intent, not details the repository or established defaults can answer. Honor the requested deliverable and existing authorization.

Select one branch

  • A material requirement, acceptance boundary, or authority decision prevents

useful progress: read [gate mode](references/gate-mode.md).

  • The user explicitly requests an interview or collaborative idea development:

read [interview mode](references/interview-mode.md).

  • Otherwise continue the original task without a clarification workflow.

A request to write or update a document is not automatically an interview. Discovery and independent authorized work may continue while a genuine human prerequisite remains unresolved.

Resume the original task

When answers or authorized assumptions settle material uncertainty, continue without requesting another approval for the same decision. Stop after the clarification or brief when that was the requested deliverable.

Use diagnosis for uncertain current-code claims and planning only when a plan is requested or needed for safe execution. These are optional next actions, not a fixed chain. Resolve and read another skill's available SKILL.md before using it; do not assume sibling installs or imitate an unavailable skill.