skills.rest
dhanesh
dhaneshCOMMUNITY
Explore all skills by this author →
Website𝕏@dhaneshpurohitGitHub

manifold-m1-constrain

Conduct structured interviews to document constraints across five domains.

8|Updated Jan 12, 2026
Search Tags:#planning#requirements#discovery#interview#product-management#constraint
One-click install
npx skills add https://github.com/dhanesh/manifold --skill manifold-m1-constrain
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manifold-m1-constrain
Source: https://github.com/dhanesh/manifold/tree/main/install/agents/codex/skills/manifold-m1-constrain
Command: npx skills add https://github.com/dhanesh/manifold --skill manifold-m1-constrain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interview-driven constraint discovery across 5 categories (business, technical, UX, security, operational) to surface constraints before implementation.

Core Features & Use Cases

  • Structured interviews across five constraint categories (business, technical, user_experience, security, operational).
  • Outputs a JSON+Markdown artifact, enabling automation and governance.
  • Supports phase-driven workflows across the manifold constraint engine for planning and execution.

Quick Start

Run /m1-constrain <feature-name> to begin constraint discovery.

Frequently Asked Questions about manifold-m1-constrain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is constraint discovery in product management and why do it early?▼

Constraint discovery identifies business, technical, UX, security, and operational limits before implementation. Surfacing these constraints early during feature planning guides design decisions and prioritization across teams to prevent rework.

How do I document product requirements and constraints for downstream automation?▼

You document constraints using a formal taxonomy of invariant, goal, and boundary types. This generates a ready JSON+Markdown artifact that feeds directly into downstream automation and governance workflows.

How do I conduct structured interviews to gather technical and business constraints?▼

Structured interviews systematically probe five categories: business, technical, user_experience, security, and operational. Running a command with the feature name initiates this guided discovery process to capture requirements accurately.

Does this constraint discovery process work for complex software features with strict security limits?▼

Yes, the process explicitly covers security and operational domains alongside business and technical needs. It enforces a formal constraint taxonomy to handle strict requirements and outputs structured artifacts for governance.

What is the best way to identify boundaries and invariants before feature planning?▼

Using a formal taxonomy to classify limits as invariants, goals, or boundaries is the best approach. It ensures rapid visibility into constraints, directly guiding design choices and cross-team prioritization.

Related Skills

Explore More Product & Management Skills→
nullhacknullhack
11

define-scope

Conduct stakeholder interviews to generate scope journals and .feature descriptions.

Community
Intermediate
dhaneshdhanesh
8

manifold-m0-init

Initialize constraint manifold scaffolds with JSON and Markdown artifacts.

Community
Intermediate
re-cinqre-cinq
20

speckit

Translate feature specifications into implementation plans with validation and tracking.

Official
Advanced
jannolan200211-ship-itjannolan200211-ship-it
1

gemini

Process direct prompts for one-shot Q&A, summaries, and generation via the Gemini CLI.

Community
Intermediate