specforge-project
/specforge-project
Use when the user wants to build, create, plan, architect, scope, or spec a software project, app, platform, agent, API, tool, SaaS product, or major development feature. This skill requires routing development-project requests through the SpecForge tool before implementation.
- Author
- argentaios ↗
- Repository
- argentos-core ↗
- Licence
- MIT
- Last repository change
- 08.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user wants to build, create, plan, architect, scope, or spec a software project, app, platform, agent, API, tool, SaaS product, or major development feature. This skill requires routing development-project requests through the SpecForge tool before implementation.
Original author description
Use when the user wants to build, create, plan, architect, scope, or spec a software project, app, platform, agent, API, tool, SaaS product, or major development feature. This skill requires routing development-project requests through the SpecForge tool before implementation.
How it works
- Trigger
- Required Flow
- Stage Discipline
- Commands
SKILL.md preview
---
name: specforge-project
description: Use when the user wants to build, create, plan, architect, scope, or spec a software project, app, platform, agent, API, tool, SaaS product, or major development feature. This skill requires routing development-project requests through the SpecForge tool before implementation.
---
# SpecForge Project Intake
Use SpecForge for development-project intake before implementation.
## Trigger
Use this skill when the user says things like:
- "I want to build a project"
- "I need to build an app/tool/platform/API"
- "Let's create a new software project"
- "Plan/spec/architect this feature"
- "Use SpecForge" or "spec forge this"
## Required Flow
1. Call the `specforge` tool with `action="handle"` and the exact latest user message.
2. Follow the returned `guidance`.
3. Keep the conversation in the current SpecForge stage until the tool advances it.
4. Do not implement, scaffold, assign tasks, or create execution work until SpecForge reaches approval/execution handoff.
5. After approval, route code/project execution to the coding family team by default and keep an operator-visible orchestration loop.
## Stage Discipline
- `project_type_gate`: ask only whether the project is GREENFIELD or BROWNFIELD.
- `intake_interview`: ask one focused intake question at a time.
- `draft_review`: draft/update the PRD or implementation spec and request feedback.
- `awaiting_approval`: wait for explicit `APPROVE` or `REQUEST CHANGES`.
- `approved_execution`: implementation handoff is allowed. Use `family.dispatch_contracted` for auditable development work with explicit `toolsAllow`, timeout, and heartbeat settings. Use `family.dispatch` for lighter development work; technical/code tasks auto-prefer the `dev-team` family specialists. Use `family.spawn` with `mode="family"` only when a specific named coding family member is required. Use `team_spawn` when the approved plan needs multiple coordinated agents with dependencies. Use `sessions_spawn` only for a single isolated background task when family/team routing does not fit. Apply ArgentOS coding skills by role: `argentos-implementation-planning` for planners, `argentos-test-driven-development` and `argentos-systematic-debugging` for implementers/debuggers, `argentos-code-verification` for reviewers/integrators, and `argentos-family-team-development` for multi-agent execution. For UI/browser proof, use Browser Use with Chrome-backed inspection instead of standalone Playwright. After handoff, keep checking `family.contract_history`, `team_status`, Redis-backed `family.message`/`family.inbox`, and completion announcements; update the operator when work starts, blocks, completes, fails, or changes scope. Mirror durable decisions, blockers, merge requests, and containment proof to the Threadmaster bus.
## Commands
- Continue intake: call `specforge` with `{"action":"handle","message":"<latest user message>"}`.
- Inspect status: call `specforge` with `{"action":"status"}`.
- Exit: call `specforge` with `{"action":"exit"}` only when the user cancels SpecForge.
Versions
The database has no other skills named specforge-project.
Database snapshot: 13.11.2026 · package version b9a084325329 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100write-review
Review a SpecForge spec as a reviewer agent, and file the review as a child spec of the spec being reviewed. Use when asked to "review spec <id>", "critique this spec", "give a second opinion on <spec>", or when a workflow hands you a spec to review. Creates the review with… - 100convert-spec
Convert an existing design/spec file into a SpecForge spec in the store. Use when the user asks to "convert <file> to a spec", "import this design doc", or "turn this markdown/HTML into a SpecForge spec". Handles two cases: an existing SpecForge-style .html is ingested as-is; a… - 100paw-ps-software-executor
Product execution specialist for SaaS, apps, AI tools, and internal software products. Trigger when user requests 'build SaaS', 'define features', 'create user flow', 'scope MVP', 'prepare build package', 'software product', 'app definition', or 'PRD creation'. - 100project-kickoff
Requirements discovery for a new software project, before any tech stack or system design. Guides the user step by step through the core need, users, domain rules, data sources, scope and constraints, and ends with a confirmed docs/requirements.md. Use this whenever someone… - 100pm-start
Entry point for the AI Product Management workflow. Use whenever someone pitches or describes an app, web app, tool, dashboard, automation or product idea and wants help turning it into something built: "help me scope this", "what's the MVP", "what should I cut for v1", "build… - 100spec
Interview the user about a feature or project, then write a spec they can build from. Use when the user wants to plan, scope or spec something before coding, or runs /spec with an idea.