pick-requirements

Pins Python and Node dependencies from design.md into requirements.txt and package.json.

1|9|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill pick-requirements-agenticgogol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pick-requirements
Source: https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul/tree/main/.claude/skills/pick-requirements
Command: npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill pick-requirements-agenticgogol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects built by multiple agent skills often end up with undeclared imports, unpinned dependencies, or version mismatches between frontend and backend. This Skill locks the dependency set early so every downstream build step works against a known, consistent stack. ## Core Features & Use Cases - Dependency selection from design.md: Reads the "Tech choices" section and lists only the libraries actually needed, avoiding speculative additions. - Pinned version files: Writes requirements.txt with pinned major versions (e.g. fastapi>=0.110,<1.0) and updates package.json dependencies the same way. - Cross-stack consistency check: Flags overlapping frontend/backend tooling so integration does not hit version conflicts later. - Use Case: After approving a design for a FastAPI plus React app, run this Skill to generate backend/requirements.txt and package.json before any component-building skills execute. ## Quick Start Use the pick-requirements skill to lock the dependencies from design.md into requirements.txt and package.json before building components.

Frequently Asked Questions about pick-requirements

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

FAQPage Schema
How do I pin Python dependencies in requirements.txt?▼

Pin major versions using range specifiers like fastapi>=0.110,<1.0 instead of bare package names. This keeps builds reproducible while still allowing compatible patch and minor updates.

When should dependencies be locked in a project pipeline?▼

Lock dependencies after the design document is approved and before any component-building steps run. This ensures every build step targets the same known dependency set rather than introducing undeclared imports.

How do I avoid version mismatches between frontend and backend?▼

Identify overlapping tooling such as shared schema or type libraries during dependency selection and note them explicitly. Recording these shared dependencies early prevents integration-stage version conflicts.

What if a later step needs a dependency not in the design?▼

Re-run the dependency selection narrowly and update requirements.txt or package.json with the new pinned library. Never leave undeclared imports in the codebase.

Should I add popular frameworks just in case I need them?▼

No. Prefer the lightest dependency that satisfies the design, including standard library alternatives. Speculative additions increase maintenance burden and the risk of version conflicts.