jinn-propose

Name: jinn-propose
Availability: InStock
Author: hackefeller

Convert change requests into Linear projects with seeded phase sub-issues.

1|Updated Sep 2, 2019

Search Tags:#workflow #planning #linear #phases #jinn #seeded-issues

Ready to run

npx skills add https://github.com/hackefeller/hominem --skill jinn-propose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jinn-propose
Source: https://github.com/hackefeller/hominem/tree/main/.claude/skills/jinn-propose
Command: npx skills add https://github.com/hackefeller/hominem --skill jinn-propose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps turn vague change requests into a structured Linear proposal by creating a parent issue that describes the problem, approach, and acceptance criteria, and seeds phases as sub-issues.

Core Features & Use Cases

Create a single parent issue that owns the entire change proposal, including problem statement, approach, and success criteria.
Seed one sub-issue per phase with clear milestones, dependencies, and top-level workstreams.
Enforce sequencing via Linear MCP fields (parentId and blockedBy) and update existing matching proposals to avoid duplication.
Supported workflow for transforming product ideas into Linear work items with traceable decisions.

Quick Start

Provide a change request in Linear and run the jinn-propose workflow to generate a parent issue and sequential phase sub-issues.

Frequently Asked Questions about jinn-propose

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

FAQPage Schema

How do I convert a change request into structured Linear work items?▼

To convert a change request into structured Linear work items, use the jinn-propose workflow to generate a parent project issue with problem statement and acceptance criteria, then seed sequential phase sub-issues with proper parentId and blockedBy relations.

Can I create Linear sub-issues with phase dependencies automatically?▼

Yes, you can create Linear sub-issues with phase dependencies automatically. The workflow seeds one sub-issue per phase and enforces sequencing via Linear MCP parentId and blockedBy fields to establish clear milestones and dependencies.

Does seeding Linear proposals require a Linear MCP connection?▼

Yes, seeding Linear proposals requires Linear MCP availability to create the parent issue and per-phase sub-issues. It also depends on the jinn-explore dependency to transform vague product ideas into traceable work items.

What's the best way to avoid duplicating existing Linear proposal issues?▼

To avoid duplicating existing Linear proposal issues, the workflow checks for and updates existing matching proposals before creating new ones. This ensures change requests are consolidated into a single parent issue without redundant project entries.

How does structuring product ideas into Linear phases work?▼

Structuring product ideas into Linear phases works by creating a single parent issue that owns the entire change proposal, including approach and success criteria, then seeding individual sub-issues for each phase with clear top-level workstreams.

When should I not use a parent issue with sub-issues for Linear planning?▼

You should not use a parent issue with sub-issues for Linear planning if your change request is already highly granular or if you lack Linear MCP availability, as the workflow depends on creating interdependent phase tasks from vague product ideas.