Feature Spec

What it does

When your agent uses it

• Tasks that involve PRD writing
• Tasks that involve Planning

Example prompts

• “/feature-spec”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Check which output files exist to determine current phase (see Phase Detection table above)
2. 2Read the main spec file's YAML frontmatter for status: DRAFT|COMPLETE
3. 3If resuming, display
4. 4If user confirms, proceed to the appropriate phase file
5. 5If no task directory found, start a new feature spec

What it can do on your machine

Read from SKILL.md and the folder at commit 858ed50. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feature Spec loads about 1.8k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 725 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~111

When it runs · the whole SKILL.md, loaded when a task matches

~1.8k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~6.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from PackmindHub/packmind at commit 858ed50, republished under its Apache-2.0 licence (© PackmindHub). 725 words, ~1,784 tokens.

name

feature-spec

description

Generate a Packmind feature specification from a GitHub issue, file, URL, or direct description. Breaks Phase 3 into 4 fine-grained approval gates (domain data structures, ports/use cases/routes, frontend components, implementation plan) to catch problems early. Routes work between the OSS sibling (../packmind) and the proprietary repo (cwd). Outputs spec artifacts under tmp/feature-specs/{slug}/ for use with /feature-sprint.

tmp/feature-specs/{slug}/
├── {slug}.md               # Main spec (status: DRAFT → COMPLETE in frontmatter)
├── discovery.md            # Phase 2 output (YAML frontmatter + markdown)
├── functional-spec.md      # Phase 2 output (informed by discovery)
├── implementation-plan.md  # Phase 3 output (includes parallel groups section)
└── context.md              # Phase 4 output (YAML frontmatter + markdown)

<feature-spec-rules>
  <rule>Execute phases SEQUENTIALLY — never skip phases</rule>
  <rule>Phases 1 and 4 proceed automatically — no approval gate</rule>
  <rule>Phases 2 and 3 require USER APPROVAL via AskUserQuestion before proceeding</rule>
  <rule>Save all artifacts under tmp/feature-specs/{slug}/ — never under tracked folders</rule>
  <rule>Use Task tool with Explore subagent for codebase research; never read 50 files yourself</rule>
  <rule>Agent NEVER implements code in this skill — output ONLY specification documents</rule>
  <rule>Main spec file has status DRAFT until Phase 4 completes</rule>
  <rule>Always record target_repo (oss | proprietary | both) decided in Phase 1; consumed by /feature-sprint</rule>
  <rule>Never invent OSS/proprietary boundaries — if unsure, ask the user</rule>
</feature-spec-rules>

© PackmindHub, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in .agents/skills/feature-spec of PackmindHub/packmind.

• SKILL.md
• phase-1-resolve-source.md
• phase-2-discovery-and-spec.md
• phase-3-implementation.md
• phase-4-finalize.md
• references/context-schema.md
• references/implementation-plan-prompt.md
• references/spec-templates.md

Open the folder on GitHubat commit 858ed50