skills.rest
IndenScale
IndenScaleCOMMUNITY
Explore all skills by this author →
GitHub

principal

...

Updated Aug 23, 2026
Search Tags:#design#documentation#requirements#adr#governance#handoff#architect
One-click install
npx skills add https://github.com/IndenScale/monoco-toolkit --skill principal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principal
Source: https://github.com/IndenScale/monoco-toolkit/tree/main/src/monoco/features/agent/resources/zh/skills/principal
Command: npx skills add https://github.com/IndenScale/monoco-toolkit --skill principal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates vague user needs into formal architectural tasks, ensuring clear intent and verifiable invariants.

Core Features & Use Cases

  • Requirement modeling & analysis using 5W2H to decompose initiatives.
  • Architectural design with interface contracts, ADRs, and explicit success criteria.
  • Intention enforcement via formal Issue tickets and detailed implementation guides.
  • Invariant guarding and governance through code-driven policies and handoff documentation.

Quick Start

Write a clear problem statement, generate an Issue with acceptance criteria, and produce an Architecture Decision Record for the proposed change.

Frequently Asked Questions about principal

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

FAQPage Schema
How do I translate vague requirements into concrete architectural tasks?▼

Vague requirements are translated into concrete architectural tasks using 5W2H analysis to decompose initiatives. This generates formal Issue tickets with verifiable acceptance criteria and Architecture Decision Records.

What is the best way to document architectural decisions for system evolution?▼

Documenting architectural decisions for system evolution is best handled by generating Architecture Decision Records (ADRs). This ensures clear intent, explicit success criteria, and invariant guarding across projects.

How do I enforce design intentions during project handoff?▼

Design intentions are enforced during handoff by creating detailed implementation guides and formal Issue tickets. This approach guarantees governance through code-driven policies and manages the issue lifecycle.

Can I use 5W2H analysis to decompose initiatives for requirement modeling?▼

Yes, 5W2H analysis is used for requirement modeling to decompose initiatives. It formalizes user needs into detailed implementation guides and interface contracts for reliable system evolution.

Does this approach support invariant guarding and issue lifecycle management?▼

Yes, invariant guarding is supported through code-driven policies, while issue lifecycle management handles governance. This ensures functional requirements are met and architectural intent is preserved.

Related Skills

Explore More Software Engineering Skills→
qa-amanqa-aman
19

requirements-elicitation

Facilitate structured stakeholder requirement elicitation across interviews, workshops, observation, and document analysis.

Community
Advanced
endorlabsendorlabs
2

endor-policy

Create and enforce Endor Labs security policies across a namespace.

Official
Advanced
cyoteecyotee

forge-fuzz-testing

Automate property-based fuzz and invariant testing of Solidity contracts with Foundry.

Community
Advanced
agentward-aiagentward-ai
19

minimal-skill

Execute small automation tasks without setup or configuration.

Community
Basic