prodcraft

Route software-development tasks through lifecycle-aware intake and gateway workflows.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/yknothing/prodcraft --skill prodcraft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prodcraft
Source: https://github.com/yknothing/prodcraft/tree/main/skills/.curated/prodcraft
Command: npx skills add https://github.com/yknothing/prodcraft --skill prodcraft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prodcraft provides a lifecycle-aware entry system that routes software-development work through intake, problem-framing, gateway, and downstream workflows to ensure governance and observability.

Core Features & Use Cases

  • Intake-first triage and routing to the appropriate workflow
  • Problem-framing to clarify direction before deeper work
  • Lifecycle orchestration and observability across gateways and workflows

Quick Start

Route a new software task through intake to Prodcraft, then follow the gateway to the appropriate workflow.

Frequently Asked Questions about prodcraft

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

FAQPage Schema
What is lifecycle-aware routing for software development workflows?

Route a new software task through the intake phase to triage and clarify direction, then follow the gateway to the appropriate downstream workflow. This end-to-end orchestration ensures proper governance and observability across all development phases.

How does intake-first triage improve workflow orchestration?

Intake-first triage improves workflow orchestration by routing software-development work through problem-framing before deeper work begins. This gateway approach ensures tasks enter the correct downstream workflows with necessary governance and visibility across phases.

When do I need a gateway for routing software development work?

You need a gateway for routing software development work when tasks require lifecycle orchestration, observability, and governance across multiple phases. It clarifies direction before deeper work and directs tasks to appropriate workflows.

Does workflow orchestration require dependencies for integration?

No dependencies are required for this workflow orchestration integration. The system specifies end-to-end orchestration, observability, and governance for development tasks across phases and routes natively.

Best way to ensure observability across workflow gateways?

The best way to ensure observability across workflow gateways is using a lifecycle-aware intake system to route software-development work. It specifies end-to-end orchestration and governance for development tasks across phases and routes.