Skills conductor-new-track
📦

conductor-new-track

Content revision r1 Safe ⚙️ External commands📁 Filesystem access

Create Conductor Tracks With Specs and Plans

New engineering work often starts without clear scope or acceptance criteria. This skill gathers inputs and produces Conductor specs, plans, metadata, and track links.

Supports: Claude Codex Code(CC)
🥉 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "conductor-new-track" from https://skillstore.io/skills/sickn33-conductor-new-track.md and its manifest at https://skillstore.io/api/skills/sickn33-conductor-new-track/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-conductor-new-track.md Signed manifest GET /api/skills/sickn33-conductor-new-track/manifest Signed lockfile GET /api/skills/sickn33-conductor-new-track/lockfile

Test it

Using "conductor-new-track". Create a feature track for team-level notification preferences.

Expected outcome:

  • A classified feature track with summary, user story, acceptance criteria, dependencies, and scope boundaries.
  • A phased implementation plan with verification after each phase.
  • A completion note that lists the generated Conductor files.

Using "conductor-new-track". Create a bug track for export jobs timing out.

Expected outcome:

A bug-focused spec covering reproduction steps, expected behavior, actual behavior, affected areas, and a repair plan.

Using "conductor-new-track". Create a refactor track for simplifying checkout state management.

Expected outcome:

  • A refactor track that records motivation, success criteria, risks, and phased implementation work.
  • A metadata record and track index entry for Conductor navigation.

Security Audit

Safe
v4 • 7/6/2026 Open versioned report

All static external command alerts are false positives caused by markdown backticks, code fences, and example paths in SKILL.md. The path traversal and network reconnaissance alerts are also false positives: they are relative documentation links and a progress heading, not dangerous behavior. No prompt injection or malicious intent was found.

1
Files scanned
434
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (66)
SKILL.md:27 SKILL.md:32 SKILL.md:33 SKILL.md:34 SKILL.md:35 SKILL.md:38 SKILL.md:39 SKILL.md:40 SKILL.md:46-53 SKILL.md:53-68 SKILL.md:68-71 SKILL.md:71-75 SKILL.md:75-79 SKILL.md:79-83 SKILL.md:83-87 SKILL.md:87-91 SKILL.md:91-97 SKILL.md:97-101 SKILL.md:101-104 SKILL.md:104-108 SKILL.md:108-111 SKILL.md:111-117 SKILL.md:117-120 SKILL.md:120-124 SKILL.md:124-127 SKILL.md:127-131 SKILL.md:131-133 SKILL.md:133-137 SKILL.md:137-139 SKILL.md:139-143 SKILL.md:143-146 SKILL.md:146-152 SKILL.md:152-155 SKILL.md:155-159 SKILL.md:159-161 SKILL.md:161-165 SKILL.md:165-167 SKILL.md:167-171 SKILL.md:171-173 SKILL.md:173-177 SKILL.md:177-181 SKILL.md:181 SKILL.md:185-186 SKILL.md:186-190 SKILL.md:190-192 SKILL.md:192-237 SKILL.md:237-243 SKILL.md:243-252 SKILL.md:252-256 SKILL.md:256-260 SKILL.md:260-313 SKILL.md:313-331 SKILL.md:331-341 SKILL.md:341-349 SKILL.md:349-355 SKILL.md:355-357 SKILL.md:357-359 SKILL.md:359-376 SKILL.md:376-378 SKILL.md:378-380 SKILL.md:380-400 SKILL.md:400-402 SKILL.md:402-404 SKILL.md:404-406 SKILL.md:406-411 SKILL.md:411-427
📁 Filesystem access (2)
SKILL.md:398 SKILL.md:399
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-conductor-new-track/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-conductor-new-track/security.svg)](https://skillstore.io/skills/sickn33-conductor-new-track?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-conductor-new-track?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-conductor-new-track/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-conductor-new-track.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). conductor-new-track security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-conductor-new-track/audits/4

BibTeX citation

@techreport{sickn33-sickn33-conductor-new-track-2026, author = {sickn33}, title = {conductor-new-track security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/sickn33-conductor-new-track/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "conductor-new-track security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-06" url: "https://skillstore.io/skills/sickn33-conductor-new-track/audits/4" identifiers: - type: other value: "skillstore:sickn33-conductor-new-track:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
85
Content
68
Community
83
Spec Compliance

What You Can Build

Feature Planning

Product engineers can turn a feature idea into a reviewed spec and phased plan.

Bug Fix Intake

Support engineers can capture reproduction steps, expected behavior, affected areas, and a repair plan.

Refactor Coordination

Technical leads can document motivation, risks, success criteria, and verification work before refactoring.

Try These Prompts

Start a Feature Track 
Create a new feature track for adding saved searches to the dashboard.
Plan a Bug Fix 
Create a bug track for login redirects failing after password reset. Ask me one question at a time.
Scope a Refactor 
Create a refactor track for separating billing logic from account settings. Include risk questions and verification steps.
Create a Constrained Migration Track 
Create a chore track for migrating analytics events. Use Conductor context, capture dependencies, define out-of-scope work, and produce a phased plan.

Best Practices

  • Review generated spec and plan text before creating files.
  • Keep each track focused on one feature, bug, chore, or refactor.
  • Use acceptance criteria and verification tasks that can be checked independently.

Avoid

  • Starting a track before Conductor context files exist.
  • Combining unrelated feature and refactor work in one track.
  • Skipping the review steps and accepting incomplete scope.

Frequently Asked Questions

What does this skill create?
It creates a Conductor track with a specification, phased plan, metadata, index page, and registry updates.
Does it write application code?
No. It plans work and creates tracking documents; implementation is handled by other workflows.
Can it handle bugs?
Yes. It asks for reproduction steps, expected behavior, actual behavior, affected areas, and optional root cause notes.
Does it require Conductor setup?
Yes. It expects conductor/product.md, conductor/tech-stack.md, and conductor/workflow.md to exist.
How does it choose a track ID?
It builds a short name from the task summary, adds the current date, and checks for collisions.
Can I edit the generated spec or plan?
Yes. The workflow asks for review before final track creation.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/conductor-new-track

Ref

01171b582d636c013315c5e0d969c64f8d9cdff2

Maintenance freshness

7/18/2026

Usage

6 downloads · 96 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all