Generate framing artifacts defining scope, success criteria, and governance for Nexus initiatives.
npx skills add https://github.com/LaPaGaYo/nexus --skill frame-lapagayo
Please help me install this Agent Skill. Skill: frame Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/canonical/frame Command: npx skills add https://github.com/LaPaGaYo/nexus --skill frame-lapagayo
Framing scope, success criteria, and governance for Nexus projects so planners and engineers share a single, authoritative starting point.
Create a framing outline for a new feature by defining the scope, success criteria, risks, and non-goals.
High-intent search queries and answers about installing and using this skill.
To define project scope and success criteria before planning, you can generate canonical framing artifacts and governance-ready outputs that formalize non-goals, risks, and alignment across stakeholders.
Writing a PRD-like document for governance workflows uses a reusable framing template to capture scope, success criteria, and decision points for disciplined planning and stakeholder alignment.
You need to formalize scope for Nexus initiatives when discovery is complete enough to define boundaries and success criteria before routing execution or integrating a plan sequence.
Yes, you can align stakeholders across governance workflows by producing authoritative framing artifacts that document scope, non-goals, and success criteria for planners and engineers.
Framing scope requires completed discovery to ensure enough context exists to accurately define success criteria, risks, and non-goals before generating governance-ready planning artifacts.
shiroginCapture project identity, principles, stakeholders, boundaries, and success criteria.
putrawitamaChallenge assumptions and expand problem framing in CEO strategic plans.
learningmatter-mitDecompose scientific workflows into chronological action plans with skill mappings.
zaeem-rafiqTranslate fuzzy product ideas into a formal PRD with structured discovery.
