skills.rest
jetteim
jetteimCOMMUNITY
Explore all skills by this author →
GitHub

shaping-features

Plan feature packets from capabilities with dependencies and architecture impact.

Updated Apr 11, 2026
Search Tags:#planning#capability#acceptance-criteria#c4#nfr#story-slicing#feature-packet
One-click install
npx skills add https://github.com/jetteim/platform-workstation-bootstrap --skill shaping-features
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shaping-features
Source: https://github.com/jetteim/platform-workstation-bootstrap/tree/main/agents/skills/codex-curated/shaping-features
Command: npx skills add https://github.com/jetteim/platform-workstation-bootstrap --skill shaping-features

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning strategic capabilities, roadmaps, or architectural shifts into concrete, deliverable feature packets with explicit acceptance criteria, non-functional requirements, enablers, dependencies, and traceability.

Core Features & Use Cases

  • Convert a capability or architecture change into a structured feature packet ready for planning and delivery.
  • Attach acceptance criteria, NFRs, dependencies, and C4 impact to each feature slice.
  • Use for roadmaps, epic planning, and incremental delivery with clear story slicing.

Quick Start

Provide a feature packet for the next capability by outlining value, dependencies, and architecture impact.

Frequently Asked Questions about shaping-features

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

FAQPage Schema
How do I convert a strategic capability into a deliverable feature packet?▼

Acceptance criteria and NFRs are attached to each feature slice to define value, dependencies, and architecture impact. This ensures clear scope and traceability across C4 levels for incremental delivery.

How do I apply story slicing to an architecture update across multiple teams?▼

Feature packet planning structures capabilities by detailing value, dependencies, and architecture impact. It ensures clear scope, traceability, and story-slicing readiness across C4 levels for roadmaps and epic planning.

Can I use feature packets for roadmap planning and incremental delivery?▼

Feature packets require capabilities, roadmaps, or architectural shifts as input to detail value, dependencies, and architecture impact. This produces structured packets with acceptance criteria, NFRs, and traceability for delivery planning.

Does feature packet planning work with C4 architecture levels?▼

Story slicing and execution tools take the structured feature packets and implement the defined slices. This converts planned capabilities with acceptance criteria and NFRs into working software increments.

What is the best way to document dependencies and non-functional requirements for a new capability?▼

Alternative planning tools structure capabilities into epics or user stories with dependencies and acceptance criteria. These provide differentiated results for teams not utilizing the feature packet or C4 architecture model.

Related Skills

Explore More Product & Management Skills→
Lev-itLev-it

value-prop-statements

Generate targeted value proposition statements from provided value propositions.

Official
Intermediate
j-cogburnj-cogburn

planning-and-task-breakdown

Decompose unstructured work items into ordered tasks with acceptance criteria.

Community
Intermediate
anukkrit149anukkrit149

c4-architecture

Generate C4 architecture diagrams in Mermaid syntax for software systems.

Community
Intermediate
liminal-ailiminal-ai
1

ls-publish-epic

Break down a validated epic into per-story files with Jira-ready formatting.

Official
Advanced