Scan the conductor directory to extract project context and plan tasks.
npx skills add https://github.com/89jobrien/steve --skill use-conductor
Please help me install this Agent Skill. Skill: use-conductor Source: https://github.com/89jobrien/steve/tree/main/steve/skills/use-conductor Command: npx skills add https://github.com/89jobrien/steve --skill use-conductor
Scan for the conductor directory at the project root and extract core context to guide work.
Run the conductor-scan to surface project direction and current tasks.
High-intent search queries and answers about installing and using this skill.
Extract project direction by scanning the conductor/ directory at your project root for core files like product.md, product-guidelines.md, tech-stack.md, workflow.md, and tracks.md. This Skill reads these files to surface product vision, guidelines, tech stack, workflow methodology, and active tracks as cohesive project context.
The conductor directory should contain product.md for vision, product-guidelines.md for guidelines, tech-stack.md for technology choices, workflow.md for methodology, and tracks.md listing active tracks. Track-specific subdirectories under tracks/<name>/ may include plan.md, spec, and metadata files for detailed planning.
Yes. Conductor files provide current project direction and next steps by consolidating product vision, workflow methodology, and active track plans. Use this unified context to align work with project goals and understand current priorities across tracks.
Yes. This Skill requires locating the conductor directory at your project root. If your project doesn't have one, you'll need to create the directory structure and populate it with the core files—product.md, product-guidelines.md, tech-stack.md, workflow.md, and tracks.md—before scanning for project context.
Identify active tracks by reading tracks.md, then access each track's current plan by navigating to tracks/<name>/plan.md. This gives you the up-to-date status, deliverables, and next steps for work within each track.
Treat conductor files as living documentation: update product.md when vision changes, refresh tech-stack.md for dependency or architecture shifts, revise workflow.md for methodology updates, and maintain tracks.md and track-specific plans as work progresses. Regular updates ensure the extracted context stays current and actionable.
chicanoandres702Generate standardized Conductor project artifacts and track registry with setup_state.json.
NnnsightnnnConvert high-level project plans into phased task breakdowns with dependencies.
liqiongyuGenerate a Product Vision Pack with context, pillars, and rollout plan.
TheSethRoseCreate and maintain a centralized product marketing context document at .claude/product-marketing-context.md.
