Plan feature development through structured pre-dev workflows with research-first gates.
npx skills add https://github.com/LerianStudio/ring --skill using-pm-team
Please help me install this Agent Skill. Skill: using-pm-team Source: https://github.com/LerianStudio/ring/tree/main/pm-team/skills/using-pm-team Command: npx skills add https://github.com/LerianStudio/ring --skill using-pm-team
10 pre-dev workflow skills + 3 research agents organized into Small Track (4 gates, <2 days) and Large Track (9 gates, 2+ days) for systematic feature planning with research-first approach.
Start a pre-dev flow for a feature: /pre-dev-full feature-name or /pre-dev-feature feature-name.
High-intent search queries and answers about installing and using this skill.
Pre-dev planning organizes feature initiatives through a structured workflow: Gate 0 research establishes feasibility, PRD captures functional requirements, TRD defines technical approach, API design specifies contracts, data modeling covers schema, dependency mapping identifies blockers, and task breakdown creates execution units. Small Track completes this in <2 days; Large Track in 2+ days with 9 gates and parallel research.
Pre-dev workflow generates research.md documenting discovery findings, PRD.md for feature requirements, TRD.md for technical decisions, API.md specifying endpoints and contracts, data-model.md defining schema, dependencies.md mapping external integrations, tasks.md for work units, and subtasks/ directory for granular execution items.
Small Track (4 gates, <2 days) suits straightforward features with minimal cross-team coordination and research needs. Large Track (9 gates, 2+ days) handles complex initiatives requiring extensive research, cross-functional reviews, API design iteration, data modeling depth, and orchestrated dependency resolution across multiple teams.
Yes. The workflow includes Gate 0 research with research agents for discovery, dedicated API design phase producing API.md contracts, and structured review gates ensuring research quality and technical feasibility before task execution begins.
PRD (Product Requirements Document) captures what the feature does—functional goals, user problems, and acceptance criteria. TRD (Technical Requirements Document) defines how to build it—architectural decisions, technology choices, data schema, and API contracts. Both are gate outputs ensuring alignment between product and engineering.
Dependency mapping identifies external integrations, service blockers, and cross-team prerequisites required for feature completion. This artifact surfaces risks early, enables parallel planning across teams, and informs task sequencing and time estimation before development begins.
Ocean326Document product problems and opportunities through structured discovery and stakeholder interviews.
camilooscargbaptistaConvert backlog items into prioritized user stories with acceptance criteria and sprint backlog.
asfbay-bitOrchestrates planning and build phases with gated, checkpointed pipeline.
LerianStudioAutomate a four-gate pre-development workflow for small software features.
