Initialize project direction with a contract-style workflow defining mission, roadmap, and technical foundation.
npx skills add https://github.com/rusi/junior --skill jr-init
Please help me install this Agent Skill. Skill: jr-init Source: https://github.com/rusi/junior/tree/main/agents/skills/jr-init Command: npx skills add https://github.com/rusi/junior --skill jr-init
Initialize or reinitialize project direction with a contract-style workflow that defines product mission, roadmap, technical foundation, and development environment before implementation starts.
Draft a product initialization contract outlining the mission, roadmap, and technical foundation before starting implementation.
High-intent search queries and answers about installing and using this skill.
To align stakeholders and define product direction before implementation, you can use a contract-style initialization workflow that specifies the product mission, roadmap, and technical foundation to set the initial scope.
The best way to initialize a new project is by drafting a product initialization contract that outlines the mission, roadmap, and technical foundation to clarify goals and obtain alignment before development begins.
You should reinitialize project direction when you experience unclear strategy, stale planning docs, or need to realign stakeholders on the product mission, roadmap, and development environment before implementation.
A contract-style project initialization generates artifacts defining the product mission, roadmap, technical foundation, and development environment to establish the process and scope required for stakeholder alignment.
Yes, this initialization workflow applies to existing projects with unclear strategy or stale planning docs, allowing you to redefine the product mission, roadmap, and technical foundation to realign stakeholders.
Defining the technical foundation and development environment before building ensures that the product mission and roadmap are technically feasible, preventing scope creep and aligning stakeholders from the start.
sohei56Transform product briefs and stakeholder input into validated requirements and an initial Product Backlog.
DanhvbPrioritize product requirements using MoSCoW, RICE, Kano, and WSJF frameworks.
ChandlerHardyManages milestones, next steps, and roadmaps in Chronicle via MCP API and CLI.
jesseotremblayAnalyze business models using the Business Model Canvas framework.
